An ansible role which configures performance analysis services for the managed host. This (optionally) includes a list of remote systems to be monitored by the managed host.
Performance Co-Pilot (PCP) v5+. All of the packages are available from the standard repositories on Fedora, CentOS 8, and RHEL 8. On RHEL 7 and RHEL 6, you will need to enable the Optional repository/channel on the managed host.
The role can optionally use Grafana v6+ (metrics_graph_service) and
Redis v5+ (metrics_query_service) on Fedora, CentOS 8, and RHEL 8.
metrics_monitored_hosts: []
List of remote hosts to be analysed by the managed host. These hosts will have metrics recorded on the managed host, so care should be taken to ensure sufficient disk space exists below /var/log for each host.
Example:
metrics_monitored_hosts: ["webserver.example.com", "database.example.com"]metrics_retention_days: 14
Retain historical performance data for the specified number of days; after this time it will be removed (day by day).
metrics_graph_service: no
Boolean flag allowing host to be setup with graphing services. Enabling this starts PCP and grafana servers for visualizing PCP metrics.
metrics_query_service: no
Boolean flag allowing host to be setup with time series query services. Enabling this starts PCP and redis servers for querying recorded PCP metrics.
metrics_into_elasticsearch: no
Boolean flag allowing metric values to be exported to Elasticsearch.
metrics_from_elasticsearch: no
Boolean flag allowing metrics from Elasticsearch to be made available.
metrics_from_mssql: no
Boolean flag allowing metrics from SQL Server to be made available. Enabling this flag requires a 'trusted' connection to SQL Server.
metrics_from_bpftrace: no
Boolean flag allowing metrics from bpftrace to be made available.
metrics_username: metrics
metrics_password: metrics
Mandatory authentication for executing dynamic bpftrace scripts.
metrics_provider: pcp
The metrics collector to use to provide metrics.
Currently Performance Co-Pilot is the only supported metrics provider. When using the PCP provider these TCP ports will be used - 44321 (pmcd, live metric value sampling), 44322 (pmproxy, with metrics_query_service or metrics_graph_service), 6379 (redis-server for metrics_query_service) and 3000 (grafana-server for metrics_graph_service).
This role does not configure for remote access to these services such as through a firewall. See https://github.com/linux-system-roles/firewall
This role does not configure SELinux for remote access to these services either. However, the pmcd and pmproxy services are in the "ephemeral" range requiring no special setup and the Grafana port is "unregistered". The Redis port is gated by the redis_port_t SELinux type and may need to be further configured, if you require direct access (not required if you are accessing it from metrics role tools like Grafana and PCP). Use https://github.com/linux-system-roles/selinux to manage port access, for SELinux contexts.
None.
Basic metric recording setup for each managed host only, with one weeks worth of data retained before culling.
- hosts: all
vars:
metrics_retention_days: 7
roles:
- linux-system-roles.metricsScalable metric recording, analysis and visualization setup for the managed hosts, providing a REST API server with an OpenMetrics endpoint, graphs and scalable querying.
- hosts: all
vars:
metrics_graph_service: yes
metrics_query_service: yes
roles:
- linux-system-roles.metricsCentralized metric recording setup for several remote hosts and scalable metric recording, analysis and visualization setup for the local host, providing a REST API server with an OpenMetrics endpoint, graphs and scalable querying.
- hosts: monitors
vars:
metrics_monitored_hosts: [app.example.com, db.example.com, nas.example.com]
metrics_graph_service: yes
metrics_query_service: yes
roles:
- linux-system-roles.metricsMIT