Adapter time stamps in BMC ProactiveNet


This section describes how the time stamp is calculated by third-party applications and displayed in BMC ProactiveNet.

During every poll, the adapter compares the previously recorded time stamp and the current time stamp for each instance. If the time stamps are different, the adapter treats this as a new data point and records the data.

If the time stamps are the same, the adapter treats this as an old data point and drops the current time and increments the duplicate-poll counter from its internal cache. The adapter continues to drop unchanged data points until the counter reaches the adjustable number (by default, 6) of duplicate data polls. When the adapter exceeds the duplicate-poll counter (for example, on the 7th poll), the adapter poll records NO_DATA and displays No Fresh Data. The time stamp for the NO_DATA poll is calculated as follows:

lastRecordedTime + [(duplicatePollCounter+1)*pollFrequency]

For example, for the following data:

  • lastRecordedTime = 8:00 A.M 
  • duplicatePollCounter = 6 
  • pollFrequency = 5 minutes

    The time stamp for the NO_DATA poll is calculated as follows:

    8:00 + [(6+1)*5] = 8:35

    After recording a NO_DATA point, the adapter continues to drop unchanged data points until it detects a new data point. When the adapter receives a new data point, the adapter resets its internal counter.

    Warning

    Note

    Do not change time stamps. Changing the time stamps causes either a gap in the data or data overlap for a particular period, depending on the time zone.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC ProactiveNet 9.6