Agents keep records of ongoing events in course of syncing and store them in storage folder in 'events' subdirectory. Events log schema is described here. These are uploaded to Management Console in real time and show up there on the following tabs:
- Events main tab
- Agents main tab
- Job run
- An agent in a job run.
Management Console receives only those events that a masked in Agent or Job profile by parameter"Console's events level". They remain in the events list in Console's UI even though the error or misconfiguration itself might have already been fixed.
All events that agents send to MC are stored locally on Management Console server in its storage folder in data\reporting\daily subdirectory. These are sqlite database files with two timestamps in their name: start and end of a record. By default each db file keeps record for a day, new db is started next day, and is deleted 90 days later. Manually deleting a database file clears the events from Console's UI. Their default time to live is 365 days. It's configurable and can be changed by adding 'ttl; into 'reporting' section in MC's configuration file. The value is in milliseconds, so 7 days = 604800000
- Source Can be Management Console itself or an Agent, depending on where the error appeared. Clicking on an agent name opens the agent's details view.
- Component can be "Global" or a specific job.
Component "Global" means that the event affect the overall Agent's misconfiguration. For example, agent's listening port if busy by another progress.
- If the error affects a job execution, corresponding job run name appears as Component.
- Component can be empty for "Management Console" source.
Most frequent Events error messages are explained here.