Management zones and Log Monitoring
Management zones are an information-partitioning mechanism that allow you to focus on specific parts of your topology. You can customize a management zone to include a specific set of monitored entities via management-zone rules. Use one of these two methods to analyze logs generated by a management-zone entity:
- Ingest logs via OneAgent, which automatically discovers log files in the topological context.
- Use generic log ingestion via API, which requires certain attributes to detect the topological context.
If you use generic log ingestion via the Log Monitoring API v2, you can send an object representing a single event or an array of objects representing multiple events. The object must contain at least one of the following attribute keys, which define the entity types for which log data is ingested.
dt.entity.process_group_instance—Process group instances
Log Monitoring checks, in the order listed above, if the log event attribute value (and, therefore, the corresponding entity) belongs to a given management zone. At the first match, Log Monitoring stops checking and assigns the log data to the management zone that the matched entity belongs to.
In the log viewer, select the Filter button in the menu bar to select a management zone. The log viewer displays log data for the entities matching the log-event attribute keys listed above.
Users must have the View logs permission on the environment level or management-zone level to be able to view the ingested and automatically assigned log data.
The log viewer displays log data for up to 10,000 monitored entities per management zone. If your management zone contains more than 10,000 monitored entities, and you would like to see log data for all of your monitored entities, you can break your management zone into smaller zones of fewer than 10,000 monitored entities each.