Bug 1299514 - Track issue of aggregated-logging and stacktraces (https://github.com/openshift/origin-aggregated-logging/issues/43)
Summary: Track issue of aggregated-logging and stacktraces (https://github.com/openshi...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Luke Meyer
QA Contact: chunchen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-18 14:48 UTC by Miheer Salunke
Modified: 2016-09-30 02:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-25 20:34:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Miheer Salunke 2016-01-18 14:48:31 UTC 
Created attachment 1115868 [details]
log

Description of problem:
We've installed the aggregated-logging Stack from https://github.com/openshift/origin-aggregated-logging/tree/master/deployment

Fluentd handels java exception stack traces line per line as a single event. Support requires error messages/stack traces as ONE event, otherwise it is hard to separate different errors recorded at the same time

Version-Release number of selected component (if applicable):
3.1

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
 https://github.com/openshift/origin-aggregated-logging/issues/43
Comment 4 ewolinet 2016-02-25 20:34:34 UTC 
Closing this to track in https://github.com/openshift/origin-aggregated-logging/issues/28 as an RFE as this is a duplicate.
Note You need to log in before you can comment on or make changes to this bug.