Log Monitoring
With Log Monitoring as a part of the Dynatrace platform, you gain direct access to the log content of all your mission-critical processes. You can create custom log metrics for smarter and faster troubleshooting. You will be able to understand log data in the context of your full stack, including real user impacts.
Log data analysis
Analyze significant log events across multiple logs, across parts of the environment (production), and potentially over a longer timeframe. Log content can be filtered based on keywords or timeframe. For immediate notification, set alerts for monitored log data. Most significantly, Dynatrace artificial intelligence automatically correlates log messages with problems it detects in your environment and factors the messages into problem root-cause analysis.
Log data alerting
Define patterns and custom log metrics to receive proactive notifications. Log Monitoring enables you to create a metric based on your monitored log data. With such a metric, you can have Dynatrace continuously scan your monitored log data and display a chart of that metric on your dashboard so that any pattern changes that occur in your custom metric will be clearly visible.
Pricing framework
Log Monitoring pricing is based on the Davis data units (DDUs) model. See DDUs for Log Monitoring for details on how DDU consumption is calculated for Log Monitoring.
Log Monitoring v1 and v2
Log Monitoring v2 is a new approach to acquiring, analyzing, and monitoring log data. Be sure to consider the following before moving to Log Monitoring v2:
- No data will be copied from Log Monitoring v1 storage.
Switching to Log Monitoring v2 will reset all of your Log Monitoring v1 data. Log Monitoring v1 data won't be accessible. - You will enable new OneAgent log module.
Log Monitoring v2 works properly with OneAgent 1.217 or later. Earlier OneAgent versions are not supported. - You will enable a limit of 10,000 events per minute.
Contact Dynatrace ONE to change this limit. - Your Log Monitoring v1 event definitions won't be accessible.
- Your Log Monitoring v1 metrics configuration won't be accessible.
Pricing for Log Monitoring v2, like Log Monitoring v1, is based on the Davis data units (DDUs) model.
| Aspect | Log Monitoring v1 | Log Monitoring v2 |
|---|---|---|
| OneAgent log module | The new OneAgent log module is backward compatible with Log Monitoring v1. The previous OneAgent log module will receive only critical bug fixes (no new features). | OneAgent versions 1.217 and later with new OneAgent log module enabled. |
| Timestamp | Log entry with unrecognized timestamp generates an error. | Log entry with unrecognized timestamp is adjusted with the current timestamp allowing the log entry to be processed. |
| Log files auto discovery | Auto discovery with OneAgent log module | Auto discovery with OneAgent log module (without special support for IIS, support for IIS is coming) |
| Manual log files configuration | Configuration on process group level (via Dynatrace UI or configuration file on a host) | Configuration on process group level (only via Dynatrace UI, configuration file on a host is coming) |
| Configure agent using the configuration file on a host | Yes | Only security flags. Other configuration options are coming. |
| Mask sensitive information for logs | Yes | Coming |
| On-demand access to log files on monitored host | Yes | No |
| Pricing framework | Based on DDU consumption (default retention period - 35 days) | Based on DDU consumption (default retention period - 35 days) |
| Data retention period | Possible to change in Settings | 35 days by default |
| Alert generation | Possible | Generate alerts based on log streamed to central storage |
| Metric generation | Possible for: occurrences and numerical value extracted from log message | Possible to define metrics based on occurrences of log event |
| Configure data stream to central storage | Log sources page in Settings | Log sources page in Settings |
| Generic log data ingestion engine | No | Yes |
FAQ
What is the limit of data that can be ingested?
Log data ingest is limited to 10,000 log events for trial accounts (automatically enabled) and 100,000 log events per minute for Dynatrace customers. This limit applies to log data provided by generic log ingestion and OneAgent. This can be increased upon request.
Who can increase the ingestion limit per tenant?
Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.
Log Monitoring v1
Data acquisition
Log content auto-discovery v1
Add log sources v1
Enable access to log content v1
Log Monitoring configuration file v1
Add log files manually v1
Log file formats v1
Log data storage v1
Analysis
Log viewer v1
Custom metrics for Log Monitoring v1
Analyze log data v1
Log Monitoring v2
Data acquisition
Log content auto-discovery
Log data formats
Generic log ingestion
Log Monitoring API v2 - POST ingest logs
Log custom attributes
Log sources and storage
Add log files manually
Log Monitoring configuration file
Analysis
Log viewer
Management zones and Log Monitoring
Log metrics
Log events
Log Monitoring API v2 - GET aggregate logs
Log Monitoring API v2 - GET search logs