Data being discarded due to different timestamp from the FMS to the Fglam client that is sending (4354854)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Data being discarded due to different timestamp from the FMS to the Fglam client that is sending
Description

Data being discarded due to different timestamp from the FMS to the Fglam client that is sending the collected data over. Any way to get this data back? How to be alerted when this happens?
Resolution

Once the FMS marks the data to be discarded, it is discarded - there is no way to get this back.

Make sure the clocks are synched up on all Fglams and FMS to prevent this.
A notification can be sent if data is being discarded for this reason by enabling a Core Monitoring Policy rule called "Catalyst Data Service Discarding Data" which sents alarms to the console. The Alarm message reads:
"Observation values are being discarded due to having timestamps outside of the allowable range from the management server time."

By default, it does not have an Email Action associated to it, but one can be created.

1. Go to the Admin Console | Administration | Rules & Notifications | Manage Rules.
2. Edit the "Catalyst Data Service Discarding Data" rule.
3. Expand Warning severity | Action tab | Add the new Email Action and define its parameters (mail.recipient, mail.subject, mail.message).

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title