[
https://issues.apache.org/jira/browse/APEXCORE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827493#comment-15827493
]
Ajay Gupta commented on APEXCORE-611:
-------------------------------------
Hi,
The below approach can be used for this JIRA. Kindly let me know your
viewpoints/suggestions.
Current event log mechanism :
The events recorded are currently written in datatorrent/apps/{appid}/events/
folder in files named part{id}.txt. When rest API call comes, we read these
files and return the list of events as List<EventInfo> objects.
a) Add a enum field like EventLogLevel in StramEvent, assign the log level in
constructors of different events like StartOperator, StartContainer,
StopOperator, etc.
b) Add eventLogLevel in EventInfo class. The events returned to gateway from
StramClient is a list of EventInfo objects.
c) Changes in EventsAgent - processPartFile to parse the eventLogLevel
> Stram Event Log Levels
> ----------------------
>
> Key: APEXCORE-611
> URL: https://issues.apache.org/jira/browse/APEXCORE-611
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Ajay Gupta
>
> Provide log levels for Stram events. Such as INFO, WARN, ERROR
> Eg:
> 1. Start Container, Start Operator are INFO level events
> 2. OperatorError is ERROR level event
> 3. Stop Container, Stop Operator are WARN level events
> Log level for events can help in user experience when showing the event list
> in a GUI. eg: In datatorrent gateway UI, we want to provide color-coded log
> levels so that user can focus more on ERROR and WARN events.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
