|Table of Content Zone|
The System Metrics Collectors
The metrics collectors run on the supervisor, one collector for each metric. They sample at 15-second intervals and report the data every 60 seconds to the Data Relay Agent (DRA). Data is sent over the HTTP protocol to the DRA.
The system metrics collectors are installed as part of the qube-system-metrics package; no post-installation configuration is necessary. They should begin running immediately after installation, check the metrics log for any messages relating to error conditions.
The system metrics collectors log location is platform-dependent:
Configuration (Linux only)
Configuration is only needed when the DRA is not running on the supervisor host (the same host as the collectors), or is listening on a port other than its default of 5001. Configuration is done through 2 environment variables:
These 2 environment variables are set by editing /etc/sysconfig/pfx_metrics and restarting the
The Data Relay Agent (DRA)
The DRA serves as a gateway between the collectors and the cloud-based metrics server. It can be installed either on the supervisor, on another host on the same network, or on a host outside of a firewall.
The DRA log
location is platform-dependent:
No configuration of the DRA is necessary for it to function as a gateway for the systems performance metrics.
Ports in use
The DRA listens for data from the system metrics collectors on port 5001.
DRA Installation Scenarios
The Metrics Server
The DRA relays data up to the metrics server over a REST API running over TLS. The metrics server's only purpose is to ingest the metrics data and store it in an InfluxDB cluster database, and is a service running behind an Elastic Load Balancer to ensure high availability and scalability.
The Metered Licensing Portal
The metered license portal is the service running at https://metered.pipelinefx.com, and is a cluster of hosts behind an Elastic Load Balancer. The website servers behind that load balancer communicate with another set of backend servers behind a separate load balancer over another REST API, and those backend servers retrieve the metrics data from the InfluxDB cluster for display on the portal site.