Dynatrace log ingestion: detecting silent failures, coverage gaps and excess volume
Log ingestion pipelines rarely fail loudly; they tend to go quiet, for example when an API token expires or a file changes format, so problems surface only during investigations or on the consumption bill. Recent Dynatrace SaaS improvements, including a ready-made dashboard, self-monitoring events from the OneAgent log module, consolidated configuration in the Settings app, and Environment ActiveGate sizing guides, make it possible to monitor log ingestion as a service in its own right. The article focuses on three common failure modes: sources that stop sending, sources never captured at all, and rules that produce excessive volume. Self-monitoring events in dt.system.events describe source health, while coverage views reveal hosts or clusters without ingest rules. The recommended routine is to pin the Log ingest overview dashboard and review component health and top producers weekly, drilling into events when a component appears degraded.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in