06-07-2019 06:21 AM
Good morning, we are in the middle of deploying Stealthwatch 7.0
I would like to schedule a report - Suspect Long Flows Alarms for example
When I view the alarms in the in the Java client - the times reflect local timezone information - yet when the scheduled report is generated - the alarms are all displayed in UTC
Has anybody else noticed this - and can this be modified to reflect local time for the alarms on the report?
Thanks in advance for any info
Solved! Go to Solution.
08-06-2019 10:38 AM
Thanks for pointing that out.
After some research changing the time reflected in Java client reporting does not seem to be configurable. At the time that was developed; normalizing time to UTC was viewed as a feature because it allowed you to compare results from two SMCs quickly.
I did bring this to the attention of the team that is developing the new web user interface response management and reporting capability.
08-06-2019 10:38 AM
Thanks for pointing that out.
After some research changing the time reflected in Java client reporting does not seem to be configurable. At the time that was developed; normalizing time to UTC was viewed as a feature because it allowed you to compare results from two SMCs quickly.
I did bring this to the attention of the team that is developing the new web user interface response management and reporting capability.
08-06-2019 11:38 AM
Thanks for the reply - I appreciate you digging into it.
I did open a TAC case back in June and they indicated similar to what you mentioned - but I had TAC submit an enhancement request as well.
Thanks,
Bob
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide