on - edited on by
HannahM
Summary: This article addresses issues in Dynatrace Log Monitoring where log-based metrics don't show data in Data Explorer or fail to trigger alerts for log-based metric events. It explains why this happens, how to identify the root cause, and steps to resolve it.
Problem
When configuring log-based metric events in Dynatrace, you may encounter the following:
- The log metric and metric event are created successfully.
- No data points appear in Data Explorer for the metric.
- Alerting does not trigger, and the alert preview shows no data.
This typically occurs due to incorrect timestamp handling or timezone mismatches in log entries.
Troubleshooting steps
-
Check if the log metric matcher has data in the Log Viewer
- If No, wait for new data to ingest.
- If Yes, move to step 2.
-
Check the metric in Data Explorer
- If Yes, escalate for metric event troubleshooting.
- If No, proceed to step 3.
-
Open the preset dashboard: “Metric & Dimension Usage + Rejections”
- Look for metric rejection reasons such as:
timestamp too old
- Look for metric rejection reasons such as:
3. If Log Metric shows timestamp-related rejections.
The range of a timestamp for accepting data that is used in metric creation is between 1 hour in the past and 10 minutes in the future. If no timestamp is provided, the server's current timestamp is used.
Verify the timestamp of the log source and proceed with the resolution.
Resolution
Create a Timestamp Rule and correct the timezone detection of log.source,
Or if required, set the correct timezone for the host from "Advanced log settings"
Timestamp configuration allows you to switch to timestamp detection in log records. This is helpful if you can’t configure the log producer.
Timestamp configuration allows you to switch to timestamp detection in log records. This is helpful if you can’t configure the log producer.
Why this helps:
Timestamp configuration ensures Dynatrace correctly interprets log timestamps and avoids metric rejection due to “timestamp too old.”
Timestamp configuration ensures Dynatrace correctly interprets log timestamps and avoids metric rejection due to “timestamp too old.”
What's next
Wait for Matching Logs
- Metric events only generate data points when new log entries match the configured pattern.
- For testing, use a generic matcher expected to appear frequently.
If this article did not help, please open a support ticket and include:
- Screenshot of the Metric Rejection Dashboard showing the rejection reason.
- Information about:
- Log source path.
- Timezone of log entries.
- Metric configuration details.
What to read next:
https://docs.dynatrace.com/docs/shortlink/lma-log-metrics
