Performance Metrics

Victoria Metrics can be configured to pull metrics from (scrape) any HTTP resource that exposes data in the Prometheus exposition format.

FMOS configures collectd, using the write_prometheus plugin1 The Write Prometheus plugin starts an internal webserver on port 9103 (configurable) and accepts scrape requests from Prometheus, an open-source monitoring system. This plugin is similar in scope to the collectd_exporter written by the Prometheus team and uses the same naming schema so it can be used as a drop-in alternative. Synopsis: LoadPlugin write_prometheus <Plugin "write_prometheus"> Port "9103" </Plugin>, to expose its metrics in this way. Collectd listens on TCP port 9103 (the same port as the Prometheus collectd exporter) and exposes metrics at http://localhost:9103/metrics. This port is never exposed to the network, irrespective of the vm_allow_outside setting.

Using Grafana with the Prometheus is FireMon's preferred metric protocol.

Connect Prometheus in Grafana

1. Log in to your Grafana account.

2. In the side menu, click Configuration.

3. Click the Data Source tab.

4. Click Add data source.

5. Select Prometheus from the list.

6. Enter a Name or use the Grafana system generated name.

7. In the HTTP section, in the URL field enter the SIP server URL.

8. In the Auth section, select the authentication type.

9. Additional fields can be configured to meet your network security guidelines. What has been provided is the minimum needed to connect to SIP.

10. Click Save & Test.

Expose the Victoria Metrics API to the network

1. Log in to the FMOS Control Panel.

2. On the toolbar, click OS > Metrics.

3. Enable the Allow outside access to Victoria Metrics field. TCP port 8428 is used for HTTP API.

4. Set the value to true.

5. When finished, click Stage Changes.

6. If no other changes are being made, click Apply Configuration.