Seeing a WARN message about a duplicate or tardy metric. What does this mean?

Document ID:  TEC1363563
Last Modified Date:  08/02/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Application Performance Management

Releases

  • CA Application Performance Management:Release:9.5
  • CA Application Performance Management:Release:9.5.5
  • CA Application Performance Management:Release:9.5.6
  • CA Application Performance Management:Release:9.6
  • CA Application Performance Management:Release:9.6.1
  • CA Application Performance Management:Release:CA APM 9.7
  • CA Application Performance Management:Release:CA APM 9.6
  • CA Application Performance Management:Release:CA APM 9.5
  • CA Application Performance Management:Release:9.7
  • CA Application Performance Management:Release:9.5.3
  • CA Application Performance Management:Release:9.5.2
  • CA Application Performance Management:Release:9.5.1
  • CA Application Performance Management:Release:9.1.7
  • CA Application Performance Management:Release:9.1.6
  • CA Application Performance Management:Release:9.1.5
  • CA Application Performance Management:Release:9.1.4

Components

  • INTROSCOPE:APMISP
  • APM AGENTS:APMAGT
Question:

  I am seeing a WARN message like below regarding a duplicate or tardy metric.  What does this mean and how can I correct them?

[WARN] [Harvest Engine Pooled Worker] [Manager.Agent] Duplicate or tardy metric value reported: SuperDomain|Custom Metric Host (Virtual)|Custom Metric Process (Virtual)|Custom Metric Agent (Virtual)|Enterprise Manager|MOM|Collectors|server.domain.com@5001:Connected (time=94235883/last closed timeslice=94235883); ignoring

Environment:
All APM supported releases.
Answer:

 Note that your metric will likely be different than the above example.  Highlighted is the standard message that you will see.

 

Duplicate or tardy metric value reported means one of the following:

1. That duplicate metrics were generated by duplicate instrumentation due to duplicate pbd files or some java scripts.

2. That there were some connectivity problem between the Agent and Collectors.

3. The EM is being overloaded.

 

Normally what happens is that the data is harvested from the Agent by the Collector.  In this case, the data that was harvested by the Collector from the Agent matched the timestamp of the data from the previous time slice. The result is a WARN message indicating that we just received the same (duplicate) or late (tardy) data.  This data is discarded and the EM continues processing data with a new time stamp.

 

This is typically due to a performance issue.  To further investigate where the slowness occurred and what is contributing to it, open an issue with CA Support.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >