Bug 1299514

Summary:	Track issue of aggregated-logging and stacktraces (https://github.com/openshift/origin-aggregated-logging/issues/43)
Product:	OpenShift Container Platform	Reporter:	Miheer Salunke <misalunk>
Component:	Logging	Assignee:	Luke Meyer <lmeyer>
Status:	CLOSED NOTABUG	QA Contact:	chunchen <chunchen>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.1.0	CC:	aos-bugs, ewolinet, wsun
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-25 20:34:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.