Events are a way to keep track of configuration changes, incidents, application crashes or infrastructure upgrades. You can associate events to a domain or an entity, and thus track its history. They can be displayed on analysis charts in order to better understand - for instance - the performance impact of a hardware upgrade.
For more information, see the following sections:
The Event Reporting module is a powerful tool used to collect and classify events, associating them to BMC TrueSight Capacity Optimization metrics.
IT events may be roughly classified in two categories: macroscopic and microscopic events.
A macroscopic event is the (potential) cause of a problem, the log of a problem, or the log of an activity.
For example, a service unavailability or a database restart are macroscopic events.
Macroscopic events are generally reported as low volumes of time-significant events. They are often reported as the result of human analysis or logging (journal).
A microscopic event is the symptom of a problem or accident, and is traced as an effect.
For example, tickets in a customer care platform are microscopic events.
Microscopic events are generally reported as high volumes of brief events. Often, the cause of these events is uncertain, and the single event only traces the microscopic effect (e.g. a specific customer could not connect to the web site).
The obvious differences, both in scope and frequency, of the above mentioned types of events lead to a distinction in the procedures used to import them into BMC TrueSight Capacity Optimization:
- Microscopic events are imported and measured as common BMC TrueSight Capacity Optimization metrics; e.g. the number of daily tickets by ticket type, the number of daily application errors by error code, and so on.
- Macroscopic events are imported (manually or automatically) with details of the single event in a separate structure
It is possible to make a distinction between two kinds of macroscopic events, based on the predictability of the event itself
- Maintenance: Maintenance activities such as backup operations or database cleaning
- Change: Activities such as hardware or software upgrades
- Generic: Other activities such as tests
- not planned:
- Incident: A cause of abnormal behavior such as link failure, database shutdown, and so on.
- Error: An effect that has been observed such as connection failure
- Problem: An undesirable behavior that is continuously observed over time, such as high response time or poor end-to-end performance
The classification of events
The following topics explain how to work with macroscopic events: