Investigate Error Logs and Annotate
A 3-step recipe with Dynatrace. We can help you get access.
Recipe · 3 steps
Investigate Error Logs and Annotate
with Dynatrace · Observability Management
Aggregate error logs, fetch records, and raise an error event.
- Aggregate error logs grouped by the supplied fields to identify which sources are producing the most error records.
- Search the matching error log records for detail, returning the most recent records first.
- Ingest an ERROR_EVENT onto the affected entities so the error spike is annotated on the Dynatrace timeline.
What you'll need to have ready
- logQuery: DQL log query filtering to error records (e.g. 'fetch logs | filter severity=="ERROR"').
- groupBy: Comma-separated fields to aggregate by (e.g. log.source,dt.entity.host).
- from: Start of the queried time range (e.g. now-1h).
- errorTitle: The title for the raised ERROR_EVENT.
- entitySelector: The entity selector the error event targets.
For your developer
Arazzo workflow dynatrace:error-log-investigation, 3 operations: aggregateLogs → searchLogs → ingestEvent. Specs on APIs.io.