โ16 Apr 2026 10:56 AM - edited โ17 Apr 2026 09:41 AM
We're excited to invite you to try the new Log Module Self-Monitoring Events feature, currently in Early Access! This capability gives you visibility into log collection health across all log modules in your environmentโwhether you're using the OneAgent log module or the Kubernetes log module. It helps you quickly spot coverage gaps, proactively detect ingestion issues, and understand which log sources are being monitored.
What you'll get:
Ready to try it? Refer to the official documentation for the full feature overview, step-by-step opt-in guide, and troubleshooting resources. Prerequisites: OneAgent version 1.333+ with the Log Module deployed via OneAgent or Dynatrace Operator. This feature is planned for General Availability in mid-2026. Your feedback before then is invaluableโtry it out, explore the dashboard, and share your thoughts by replying to this thread!
โ16 Apr 2026 11:01 AM
Hi,
Nice, I have 2 questions in relation to this:
Thank you!
Best regards
โ16 Apr 2026 11:30 AM
Hi!
Licensing: Correctโno license is consumed for Log module self-monitoring events. They're treated as system data.
Extension logs: Extensions have their own health mechanisms, and rejected log records are already visible in the built-in "Log ingest overview" dashboard, which is a central place for log ingest monitoring. If you have specific extension log monitoring use cases in mind, feel free to share them so the PM team can analyze them.
Thanks!
โ16 Apr 2026 02:05 PM
Hi,
I was thinking in databases extensions (SQL + Oracle) mainly.
Best regards
Featured Posts