All Apps and Add-ons

Checkpoint time-stamp in future

pgsery
Explorer

The checkpoint time-stamp stored in scom_event/alert_checkpoint is getting set in the future. When the powershell script sets the checkpoint, it uses the most recent date/time from the event log data (or alert data). The new checkpoint will be in the future if any client machine clock is misconfigured in the future. This prevents new data from being processed because the script only processes events newer than the checkpoint (TimeGenerated > $event_cp).

A simple fix would use the scom server's clock to set the checkpoint. That solution would, I thnik, duplicate results for clients with clocks misconfigured in the future. However, this would be less onerous than the current situation.

Tags (1)

pgsery
Explorer

I partially solved the problem by substituting the timeadded for timegenerated field. Timeadded is the time the scom db records an event.

0 Karma
Get Updates on the Splunk Community!

Optimize Cloud Monitoring

  TECH TALKS Optimize Cloud Monitoring Tuesday, August 13, 2024  |  11:00AM–12:00PM PST   Register to ...

What's New in Splunk Cloud Platform 9.2.2403?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2403! Analysts can ...

Stay Connected: Your Guide to July and August Tech Talks, Office Hours, and Webinars!

Dive into our sizzling summer lineup for July and August Community Office Hours and Tech Talks. Scroll down to ...