Built-In Event Types

VividCortex comes pre-packaged with a number of automatically-detected events. You can also send your own custom events by following the instructions here. This is an alphabetized list of the events which you may see in the VividCortex application. You can set up an alert to trigger when any of these events has occurred using the Alerts page.

Approaching Max MySQL Connections
  • The number of connections to the database has reached 95% of the database’s current configured limit.
Balancer Round Complete
  • The MongoDB balancer has finished rebalancing data between the shards. More information about the MongoDB balancer is available in the MongoDB documentation.
Database Configuration Change
  • The VividCortex agent detected a change in the configuration of the database being monitored. The agent will detect runtime configuration changes as well as changes applied after a database is restarted.
Database Server Restart
  • The database being monitored by VividCortex has been restarted.
Disk Device Almost Full
  • The disk device is 90% full. This is configurable; contact Support for help.
Disk Device Full
  • The disk device is greater than 95% full. This is configurable; contact Support for help.
High Swap Activity
  • Swap activity on this disk device has exceeded 100 pages per second.
Long-running autovacuum
  • The PostgreSQL vacuum process took longer than the configured VividCortex threshold.
Max MySQL Connections Reached
  • The database has reached its maximum number of connections.
MongoDB Server Stall
  • This event, along with corresponding types for other supported databases, represents a Fault that VividCortex detected. Faults are short stalls that are usually caused by a bottleneck in the database’s workload. Refer to the Faults Page for details on how faults work.
Out of Memory Killer
  • The Linux Out of Memory (OOM) Killer has killed a process. The process will be named in the event.
PostgreSQL Server Stall
  • This event, along with corresponding types for other supported databases, represents a Fault that VividCortex detected. Faults are short stalls that are usually caused by a bottleneck in the database’s workload. Refer to the Faults Page for details on how faults work.
Replica Set State Change
  • The MongoDB node in a replica set has changed state; for example, it may now be a primary or a second. A complete list of replica states can be found on the MongoDB documentation.
Replica Sync Completed
  • The MongoDB node has finished fetching data from the primary.
Replica Sync Started
  • The MongoDB node is out of sync and fetching data from the primary.
MySQL Replication Started
  • The VividCortex agent has detected that replication has started running for a replica database. The event will specify whether START SLAVE was seen when replication started.
MySQL Replication Stopped
  • The VividCortex agent has detected that replication has stopped running for a replica database. The event will specify whether STOP SLAVE was seen when replication stopped.
MySQL Server Stall
  • This event, along with corresponding types for other supported databases, represents a Fault that VividCortex detected. Faults are short stalls that are usually caused by a bottleneck in the database’s workload. Refer to the Faults Page for details on how faults work.
Threshold Alert
  • A specific metric has exceeded a user-defined Threshold that was previously set for it. Metric Threshold events can be defined from the Alerts Tab in the Environment Setting Page.
New Important Query
  • A previously unseen query has appeared among the top 10 queries in the environment. Similar to the New Important Process type.
New Important Process
  • This event is similar to the New Important Query type - it indicates that a previously unseen process has appeared among the top 10 processes in the environment.

VividCortex Diagnostic Events

  • In addition to the events above, which provide information about your operating system(s) or database(s), the following events provide information about the VividCortex service. For more information about these events or if you would like help with a resolution, please contact Support.
Agent Shutdown
  • This event indicates a VividCortex agent has stopped running. The event reports the specific agent that stopped, and also reports the manner in which it was stopped (e.g. graceful shutdown or a process kill).
Agent Startup
  • This event indicates a VividCortex agent has started running. The event reports the specific agent that started, along with its version.
Database Connection Error
  • The monitoring agent is no longer able to connect to a previously-monitored database. For example, this can be because the database is refusing connections or is down.
High Distinct Query Rate
  • VividCortex has received a very high number of unique query digests. Too many unique query digests prevents aggregation of data in a way that is meaningful. To continue providing useful data, we automatically adjust the digestion algorithm to be more aggressive, which allows the system to better detect queries which are similar to one another, with only small differences which affect digestion but not query behavior.
Host Registration
  • The agent attempted to register a new database host and failed. This can be because there are no licenses available for the new database, or because of a failure in the API.
Host stopped sending data
  • The API has not received any new metrics from a registered host in the last 15 minutes. This can be caused by connection problems, or a host being shutdown.
MySQL Open Tables Tracking Stopped
  • A database has more open tables than the agent is configured to track, so table tracking has been disabled to prevent any potential performance problems. By default the agent will capture metrics on the open tables that MySQL is using, but since doing so is expensive this monitoring is automatically disabled if too many tables are open. If you would like these metrics enabled contact Support for assistance in changing the limit.
Intermittent Connectivity to Datacenter!
  • The VividCortex agent experienced a connection timeout while attempting to report metrics to the VividCortex API. If this event shows up in your environment, it could indicate a networking problem that will lead to missing data in your environment if not addressed.
Query Samples Unavailable
  • A database host’s configuration does not allow the VividCortex agent to collect samples of queries that ran on the host. This is only applicable for hosts that are using the off-host monitoring configuration.
Size Metrics Aborted
  • VividCortex has automatically disabled trying to fetch database and table sizes on this host because the database has taken too long to respond. This is done in order to prevent adding more load to a database possibly under heavy load.
Stale Action
  • One of our monitoring agent’s queries took longer than expected. This is typically caused by high load on the database, a server stall, or some other database performance issue. When this happens, it can correspond to some metrics missing for a few seconds on the affected host.
No TCP Captured
  • The agent has not detected any TCP traffic on any of the ports it is configured to monitor. The agent will restart itself in an attempt to correct for any errors, but if the problem continues you should check that traffic is being sent to the database on the correct IP/port, or contact Support.