Initialize/re-initialize the DB Collector

Summary: Initialize/re-initialize the DB collector

Description: Sent when database collector has successfully started. This happens when you configure a new collector, start/restart the agent process (in which case you'll see this event once for each collector), or when the collector recovers from a failure to communicate with the monitored database (for example, when the database goes down for a while, then comes back).

Severity: Info

Initialize/re-initialize the Hardware Metric Collector

Summary: Initialize/re-initialize the hardware metric collector

Description: Same as the above, but refers to a hardware collector, not a database collector.

This is sent when hardware collector has successfully started. This happens when you configure a new collector, start/restart the agent process (in which case you'll see this event once for each collector), or when the collector recovers from a failure to communicate with the monitored hardware (for example, when the system goes down for a while, then comes back).

Severity: Info

Server Parameter [?] has been Changed from [?] to [?]

Summary: Server parameter [?] has been changed from [?] to [?]

Description: The Database Agent constantly monitors database configuration parameters. When a parameter changes, which generally means a database administrator made a deliberate change, the agent sends this event. Splunk AppDynamics Database Visibility users can use these events to track configuration changes in their databases.

Severity: Info