Here’s a quick overview of each VividCortex agent’s functionality. For information on the the actual configuration settings available please refer to the general configuration and configuration flags pages.
This agent gathers basic identifying information about the host operating system and database server (MySQL, PostgreSQL…), and registers them with VividCortex’s API, so agents can refer to a host ID when sending metrics. It installs, upgrades, starts, stops, and supervises other agents.
This is an aggregator/gateway similar to StatsD. It listens for UDP packets with time-series metrics and sends them to VividCortex’s APIs periodically.
This MongoDB monitoring agent primarily watches
serverStatus() once per second, capturing metrics
that will later display as charts in our interface. It detects server restarts, that are reported as
events in VividCortex. It will run
buildInfo() as well upon startup, or every time the server is
This MongoDB monitoring agent decodes network traffic and sends metrics about requests to MongoDB to vc-aggregator. Queries are digested but this agent will occasionally capture samples as well, although you can disable this feature if required. This agent is a completely passive observer.
This MySQL monitoring agent primarily watches
SHOW STATUS once per second. It also captures data about
replication delay and server configuration changes. It runs some commands occasionally, such as
PROCESSLIST (during a fault, it runs these commands more frequently). It’s also able to capture queries out of
PERFORMANCE_SCHEMA, thus reading query metrics even if the setup doesn’t allow using the sniffer (see
vc-mysql-query). This is an optional feature that turns essential when using instances at Amazon RDS, for
This MySQL monitoring agent decodes network traffic and sends metrics about query behavior to vc-aggregator. The metric names are created with a checksum, so no sensitive information is revealed. This agent does NOT connect to or interact with MySQL in any way. It is a completely passive observer.
This PostgreSQL monitoring agent primarily watches status and metric views once per second. It’s also able to
capture queries out of PostgreSQL’s
pg_stat_statements, provided the extension is available. This makes up for
query metrics in situations where the use of a sniffer is not possible (see vc-pgsql-query), like for Amazon
This PostgreSQL monitoring agent decodes network traffic and sends metrics about query behavior to vc-aggregator. The metric names are created with a checksum, so no sensitive information is revealed. This agent does NOT connect to or interact with PostgreSQL in any way. It is a completely passive observer.
This Redis monitoring agent primarily runs the
INFO command once a second. It also detects server
configuration changes and faults.
This Redis monitoring agent decodes network traffic and sends metrics about requests to Redis to vc-aggregator.
This agent reads from the
/proc filesystem and sends time-series metrics such as disk, CPU, memory, and
network stats to vc-aggregator.