Circonus Inside is a robust distributed system for the collection and analysis of telemetry data.
Components and Their Purpose
This section details the operation of the various components that make up Circonus Inside.
The API service provides a REST-based programming interface for scripts and tools to interact programmatically with the product. See API sizing.
The CA is responsible for managing the Public Key Infrastructure (PKI) required by Circonus Inside. Any component that is likely to talk over a hostile network does so over SSL/TLS, requiring both valid client and server credentials. See CA sizing.
The CAQL Broker allows for alerting on Circonus Analytics Query Language (CAQL) transforms of incoming metric streams.
IRONdb is a fault-tolerant, distributed time-series database. This component manages all telemetry that is collected. It powers many features of the overall product, but most notably the visualizations available via the Web Frontend. See Data Storage sizing.
Please note that while IRONdb® can operate as a standalone TSDB, when it is operated as part of a full Circonus deployment, it is configured slightly differently and is only managed through Hooper. There is no need to install any IRONdb packages yourself.
The Enterprise Broker is responsible for collecting telemetry from canonical sources. It can actively/synthetically query networked services for information, as well as passively receive telemetry via the network. All collected telemetry is passed back to the core system via Stratcon. See Enterprise Broker sizing.
The Enterprise Broker is provisioned outside of the processes used for provisioning Circonus Inside.
The Fault Detection component is the online, complex-event processing engine. It is responsible for interpreting all telemetry data in real-time and detecting anomalous behavior. See Fault Detection sizing.
Hooper is the built-in configuration management system. It is responsible for initial configuration and installation of all other components, as well as most ongoing maintenance tasks. Hooper runs on all Circonus Inside systems except the Enterprise Broker. Hooper has no special sizing requirements.
The Hub is responsible for many ongoing operational tasks. It runs several daemons and scheduled jobs that perform routine maintenance operations. See Hub sizing.
The Long-tail Store is nothing more than a dumping zone for all the raw telemetry data collected. It can be used to reconstruct Data Storage or do out-of-band analysis on raw data. It is also the easiest source from which to backup raw measurement data. Retention of this data is left up to the operator. The Long-tail Store data may be deleted without any ill-effect on regular system usage. See Long-tail Store sizing.
Message Queue (MQ) is the brokered message queuing infrastructure over which many components communicate. See MQ sizing.
The Notification component is the case management system. Given the overall state of the system, it combines metadata about the telemetry streams and Fault Detection outputs regarding anomalous behavior to open cases (alerts) and notify interested parties. See Notification sizing.
Stratcon is responsible for accepting brokered telemetry and distributing it to all components. It stores processed data in Data Storage, publishes data in real-time to other system components via MQ, and journals raw data back to Long-tail Storage. See Stratcon sizing.
Web DB is a relational database (PostgreSQL) that stores all metadata for Circonus Inside. This includes user, account, configuration, graph, and worksheet information. All information, aside from the data itself (stored in Data Storage), is held in Web DB. See Web DB sizing.
Web Frontend is the browser-based portal through which the product is regularly used. See Web Frontend sizing.
The Web Stream component is responsible for out-of-band, real-time streaming of telemetry data for the “play” feature in graphs and dashboards. See Web Stream sizing.