Chapter 11. Setting up graphical representation of PCP metrics


Using a combination of pcp, grafana, pcp redis, pcp bpftrace, and pcp vector provides graphical representation of the live data or data collected by Performance Co-Pilot (PCP).

11.1. Setting up PCP with pcp-zeroconf

This procedure describes how to set up PCP on a system with the pcp-zeroconf package. Once the pcp-zeroconf package is installed, the system records the default set of metrics into archived files.

Procedure

  • Install the pcp-zeroconf package:

    # dnf install pcp-zeroconf
    Copy to Clipboard Toggle word wrap

Verification

  • Ensure that the pmlogger service is active, and starts archiving the metrics:

    # pcp | grep pmlogger
     pmlogger: primary logger: /var/log/pcp/pmlogger/localhost.localdomain/20200401.00.12
    Copy to Clipboard Toggle word wrap

11.2. Setting up a Grafana server

Grafana generates graphs that are accessible from a browser. The Grafana server is a back-end server for the Grafana dashboard. It listens, by default, on all interfaces, and provides web services accessed through the web browser. The grafana-pcp plugin interacts with the pmproxy daemon in the backend.

This procedure describes how to set up a Grafana server.

Prerequisites

Procedure

  1. Install the following packages:

    # dnf install grafana grafana-pcp
    Copy to Clipboard Toggle word wrap
  2. Restart and enable the following service:

    # systemctl restart grafana-server
    # systemctl enable grafana-server
    Copy to Clipboard Toggle word wrap
  3. Open the server’s firewall for network traffic to the Grafana service.

    # firewall-cmd --permanent --add-service=grafana
    success
    
    # firewall-cmd --reload
    success
    Copy to Clipboard Toggle word wrap

Verification

  • Ensure that the Grafana server is listening and responding to requests:

    # ss -ntlp | grep 3000
    LISTEN  0  128  *:3000  *:*  users:(("grafana-server",pid=19522,fd=7))
    Copy to Clipboard Toggle word wrap
  • Ensure that the grafana-pcp plugin is installed:

    # grafana-cli plugins ls | grep performancecopilot-pcp-app
    
    performancecopilot-pcp-app @ 5.1.1
    Copy to Clipboard Toggle word wrap

11.3. Accessing the Grafana web UI

This procedure describes how to access the Grafana web interface.

Using the Grafana web interface, you can:

  • Add PCP Redis, PCP bpftrace, and PCP Vector data sources
  • Create dashboard
  • View an overview of any useful metrics
  • Create alerts in PCP Redis.

Prerequisites

Procedure

  1. On the client system, open http://<grafana_server_IP_address_or_hostname>:3000 in your browser.
  2. For the first login, enter admin in both the Email or username and Password field.

    Grafana prompts to set a New password to create a secured account.

  3. In the menu, navigate to Administration and then click Plugins.
  4. In the Plugins tab, type performance co-pilot in the Search Grafana plugins text box and then click Performance Co-Pilot (PCP) plugin.
  5. In the Plugins / Performance Co-Pilot pane, click Enable.
  6. Click the Grafana icon grafana home page whirl icon . The Grafana Home page is displayed.

    Figure 11.1. Home Dashboard

    Note

    The top right corner of the screen has a settings (gear) icon grafana gear icon1 that controls the general Dashboard settings.

  7. In the Grafana Home page, click Add your first data source to add PCP Redis, PCP bpftrace, and PCP Vector data sources. For more information about adding data source, see:

  8. Optional: From the menu, hover over the admin profile icon grafana logout option icon to update your Profile, view Notification history, Change password, or to Sign out.

11.4. Configuring secure connections for Grafana

You can establish secure connections between Grafana and Performance Co-Pilot (PCP) components. Establishing secure connections between these components helps prevent unauthorized parties from accessing or modifying the data being collected and monitored.

Prerequisites

  • PCP is installed. For more information, see Installing and enabling PCP.
  • The Grafana server is configured. For more information, see Setting up a Grafana server.
  • The private client key is stored in the /etc/grafana/grafana.key file. If you use a different path, modify the path in the corresponding steps of the procedure.

    For details about creating a private key and certificate signing request (CSR), as well as how to request a certificate from a certificate authority (CA), see your CA’s documentation.

  • The TLS client certificate is stored in the /etc/grafana/grafana.crt file. If you use a different path, modify the path in the corresponding steps of the procedure.

Procedure

  1. As a root user, open the /etc/grafana/grafana.ini file and adjust the following options in the [server] section to reflect the following:

    protocol = https
    cert_key = /etc/grafana/grafana.key
    cert_file = /etc/grafana/grafana.crt
    Copy to Clipboard Toggle word wrap
  2. Ensure grafana can access the certificates:

    # su grafana -s /bin/bash -c \
      'ls -1 /etc/grafana/grafana.crt /etc/grafana/grafana.key'
    /etc/grafana/grafana.crt
    /etc/grafana/grafana.key
    Copy to Clipboard Toggle word wrap
  3. Restart and enable the Grafana service to apply the configuration changes:

    # systemctl restart grafana-server
    # systemctl enable grafana-server
    Copy to Clipboard Toggle word wrap

Verification

  1. On the client system, open a browser and access the Grafana server machine on port 3000, using the https://192.0.2.0:3000 link. Replace 192.0.2.0 with your machine IP.
  2. Confirm the lock icon lock icon is displayed beside the address bar.

    Note

    If the protocol is set to http and an HTTPS connection is attempted, you will receive a ERR_SSL_PROTOCOL_ERROR error. If the protocol is set to https and an HTTP connection is attempted, the Grafana server responds with a “Client sent an HTTP request to an HTTPS server” message.

11.5. Configuring PCP Redis

Use the PCP Redis data source to:

  • View data archives
  • Query time series using pmseries language
  • Analyze data across multiple hosts

Prerequisites

Procedure

  1. Install the redis package:

    # dnf install redis
    Copy to Clipboard Toggle word wrap
  2. Start and enable the following services:

    # systemctl start pmproxy redis
    # systemctl enable pmproxy redis
    Copy to Clipboard Toggle word wrap
  3. Restart the Grafana server:

    # systemctl restart grafana-server
    Copy to Clipboard Toggle word wrap

Verification

  • Ensure that the pmproxy and redis are working:

    # pmseries disk.dev.read
    2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
    Copy to Clipboard Toggle word wrap

    This command does not return any data if the redis package is not installed.

11.6. Configuring secure connections for PCP redis

You can establish secure connections between performance co-pilot (PCP), Grafana, and PCP redis. Establishing secure connections between these components helps prevent unauthorized parties from accessing or modifying the data being collected and monitored.

Prerequisites

  • PCP is installed. For more information, see Installing and enabling PCP.
  • The Grafana server is configured. For more information, see Setting up a Grafana server.
  • PCP redis is installed. For more information, see Configuring PCP Redis.
  • The private client key is stored in the /etc/redis/client.key file. If you use a different path, modify the path in the corresponding steps of the procedure.

    For details about creating a private key and certificate signing request (CSR), as well as how to request a certificate from a certificate authority (CA), see your CA’s documentation.

  • The TLS client certificate is stored in the /etc/redis/client.crt file. If you use a different path, modify the path in the corresponding steps of the procedure.
  • The TLS server key is stored in the /etc/redis/redis.key file. If you use a different path, modify the path in the corresponding steps of the procedure.
  • The TLS server certificate is stored in the /etc/redis/redis.crt file. If you use a different path, modify the path in the corresponding steps of the procedure.
  • The CA certificate is stored in the /etc/redis/ca.crt file. If you use a different path, modify the path in the corresponding steps of the procedure.

Additionally, for the pmproxy daemon:

  • The private server key is stored in the /etc/pcp/tls/server.key file. If you use a different path, modify the path in the corresponding steps of the procedure.

Procedure

  1. As a root user, open the /etc/redis/redis.conf file and adjust the TLS/SSL options to reflect the following properties:

    port 0
    tls-port 6379
    tls-cert-file /etc/redis/redis.crt
    tls-key-file /etc/redis/redis.key
    tls-client-key-file /etc/redis/client.key
    tls-client-cert-file /etc/redis/client.crt
    tls-ca-cert-file /etc/redis/ca.crt
    Copy to Clipboard Toggle word wrap
  2. Ensure redis can access the TLS certificates:

    # su redis -s /bin/bash -c \
      'ls -1 /etc/redis/ca.crt /etc/redis/redis.key /etc/redis/redis.crt'
    /etc/redis/ca.crt
    /etc/redis/redis.crt
    /etc/redis/redis.key
    Copy to Clipboard Toggle word wrap
  3. Restart the redis server to apply the configuration changes:

    # systemctl restart redis
    Copy to Clipboard Toggle word wrap

Verification

  • Confirm the TLS configuration works:

    # redis-cli --tls --cert /etc/redis/client.crt \
        --key /etc/redis/client.key \
        --cacert /etc/redis/ca.crt <<< "PING"
    PONG
    Copy to Clipboard Toggle word wrap

    Unsuccessful TLS configuration might result in the following error message:

    Could not negotiate a TLS connection: Invalid CA Certificate File/Directory
    Copy to Clipboard Toggle word wrap

After adding the PCP Redis data source, you can view the dashboard with an overview of useful metrics, add a query to visualize the load graph, and create alerts that help you to view the system issues after they occur.

Prerequisites

Procedure

  1. Log into the Grafana web UI.
  2. In the Grafana Home page, click Add your first data source.
  3. In the Add data source pane, type redis in the Filter by name or type text box and then click PCP Redis.
  4. In the Data Sources / PCP Redis pane, perform the following:

    1. Add http://localhost:44322 in the URL field and then click Save & Test.
    2. Click Dashboards tab Import PCP Redis: Host Overview to see a dashboard with an overview of any useful metrics.
    3. Optional: In the drop-down menu next to the clock icon grafana clock icon , you can set the timeline of the displayed metrics either by setting the absolute time range or by selecting a predefined range. You can also use the zoom out icon grafana zoom out icon to modify the displayed time range.

      Note

      The time frame displayed by default might not be aligned with the time frame covered by the archive files created by the pmlogger service.

      Figure 11.2. PCP Redis: Host Overview

  5. Add a new panel:

    1. From the plus sign grafana plus sign1 drop-down menu, select New dashboard.
    2. From the Add grafana add drop down drop-down menu, select Visualization.
    3. In the Query tab, select the pcp-redis-datasource as the Data source.
    4. In the text field below A, enter metric, for example, kernel.all.load to visualize the kernel load graph.
    5. Optional: From the Time series drop-down menu on the right, select another format of visualization, for example, Bar chart, Table, or Heatmap.
    6. Optional: Add Panel title and Description, and update other options.
    7. Click Save to apply changes and save the dashboard. Add Title.
    8. Click Apply to apply changes and go back to the dashboard.

      Figure 11.3. PCP Redis query panel

  6. Create an alert rule:

    1. In the PCP Redis query panel, click Alert grafana alert and then click New alert rule.
    2. Enter alert rule name.
    3. Define query and alert condition.
    4. Set evaluation behavior.
    5. Optional: Add annotations.
    6. Add labels and notifications.
    7. Click Save rule an exit to apply changes in alert rules.
    8. Click Apply to apply changes and go back to the dashboard.

      Figure 11.4. Creating alerts in the PCP Redis panel

      To add a notification channel for the created alert rule to receive an alert notification from Grafana, see Adding notification channels for alerts.

11.8. Adding notification channels for alerts

By adding notification channels, you can receive an alert notification from Grafana whenever the alert rule conditions are met and the system needs further monitoring.

You can receive these alerts after selecting any one type from the supported list of notifiers, which includes:

  • Alertmanager
  • Cisco Webex Teams
  • DingDing
  • Discord
  • Email
  • Google Chat
  • Kafka REST Proxy
  • LINE
  • Microsoft Teams
  • OpsGenie
  • PagerDuty
  • Pushover
  • Sensu Go
  • Slack
  • Telegram
  • Threema Gateway
  • VictorOps
  • WeCom
  • Webhook

Prerequisites

Procedure

  1. Configure SMTP and add a valid sender’s email address in the /etc/grafana/grafana.ini file:

    [smtp]
    enabled = true
    from_address = <sender_email_address>
    Copy to Clipboard Toggle word wrap
  2. Restart the Grafana server.

    # systemctl restart grafana-server.service
    Copy to Clipboard Toggle word wrap
  3. From the menu, select Alerting Contact points + Add contact point.

    Figure 11.5. Alerting in Grafana

  4. In the Create contact point details view, perform the following:

    1. Enter your name in the Name text box.
    2. Select the Integration type, for example, Email and enter the email address or multiple email addresses.
    3. Optional: Configure Optional Email settings and Notification settings.
  5. Click Save contact point.
  6. Select a notification channel in the alert rule:

    1. From the Alerting menu, select Notification policies.
    2. Click the three dots icon grafana 3 dots on the far right of Default policy and select Edit.
    3. Choose the Contact point you have just created and click Update default policy.
    4. Optional: Configure a nested policy in addition to the default policy.
    5. Optional: Configure Mute Timings.

You can setup authentication using the scram-sha-256 authentication mechanism, which is supported by PCP through the Simple Authentication Security Layer (SASL) framework.

Procedure

  1. Install the sasl framework for the scram-sha-256 authentication mechanism:

    # dnf install cyrus-sasl-scram cyrus-sasl-lib
    Copy to Clipboard Toggle word wrap
  2. Specify the supported authentication mechanism and the user database path in the pmcd.conf file:

    # vi /etc/sasl2/pmcd.conf
    
    mech_list: scram-sha-256
    
    sasldb_path: /etc/pcp/passwd.db
    Copy to Clipboard Toggle word wrap
  3. Create a new user:

    # useradd -r metrics
    Copy to Clipboard Toggle word wrap

    Replace metrics by your user name.

  4. Add the created user in the user database:

    # saslpasswd2 -a pmcd metrics
    
    Password:
    Again (for verification):
    Copy to Clipboard Toggle word wrap

    To add the created user, you are required to enter the metrics account password.

  5. Set the permissions of the user database:

    # chown root:pcp /etc/pcp/passwd.db
    # chmod 640 /etc/pcp/passwd.db
    Copy to Clipboard Toggle word wrap
  6. Restart the pmcd service:

    # systemctl restart pmcd
    Copy to Clipboard Toggle word wrap

Verification

  • Verify the sasl configuration:

    # pminfo -f -h "pcp://127.0.0.1?username=metrics" disk.dev.read
    Password:
    disk.dev.read
    inst [0 or "sda"] value 19540
    Copy to Clipboard Toggle word wrap

11.10. Installing PCP bpftrace

Install the PCP bpftrace agent to introspect a system and to gather metrics from the kernel and user-space tracepoints.

The bpftrace agent uses bpftrace scripts to gather the metrics. The bpftrace scripts use the enhanced Berkeley Packet Filter (eBPF).

This procedure describes how to install a pcp bpftrace.

Prerequisites

Procedure

  1. Install the pcp-pmda-bpftrace package:

    # dnf install pcp-pmda-bpftrace
    Copy to Clipboard Toggle word wrap
  2. Edit the bpftrace.conf file and add the user that you have created in Setting up authentication between PCP components:

    # vi /var/lib/pcp/pmdas/bpftrace/bpftrace.conf
    
    [dynamic_scripts]
    enabled = true
    auth_enabled = true
    allowed_users = root,metrics
    Copy to Clipboard Toggle word wrap

    Replace metrics by your user name.

  3. Install bpftrace PMDA:

    # cd /var/lib/pcp/pmdas/bpftrace/
    # ./Install
    Updating the Performance Metrics Name Space (PMNS) ...
    Terminate PMDA if already installed ...
    Updating the PMCD control file, and notifying PMCD ...
    Check bpftrace metrics have appeared ... 7 metrics and 6 values
    Copy to Clipboard Toggle word wrap

    The pmda-bpftrace is now installed, and can only be used after authenticating your user. For more information, see Viewing the PCP bpftrace System Analysis dashboard.

Using the PCP bpftrace data source, you can access the live data from sources which are not available as normal data from the pmlogger or archives

In the PCP bpftrace data source, you can view the dashboard with an overview of useful metrics.

Prerequisites

Procedure

  1. Log into the Grafana web UI.
  2. In the menu, navigate to Connections Data sources + Add new data source.
  3. In the Add data source pane, type bpftrace in the Filter by name or type text box and then click PCP bpftrace.
  4. In the Data Sources / pcp-bpftrace-datasource pane, perform the following:

    1. Add http://localhost:44322 in the URL field.
    2. Toggle the Basic Auth option and add the created user credentials in the User and Password field.
    3. Click Save & Test.

      Figure 11.6. Adding PCP bpftrace in the data source

    4. Click Dashboards tab Import PCP bpftrace: System Analysis to see a dashboard with an overview of any useful metrics.

      Figure 11.7. PCP bpftrace: System Analysis

11.12. Installing PCP Vector

Install a pcp vector data source to show live, on-host metrics from the real-time pmwebapi interfaces. This data source is intended for on-demand performance monitoring of an individual host and includes container support.

Prerequisites

Procedure

  1. Install the pcp-pmda-bcc package:

    # dnf install pcp-pmda-bcc
    Copy to Clipboard Toggle word wrap
  2. Install the bcc PMDA:

    # cd /var/lib/pcp/pmdas/bcc
    # ./Install
    [Wed Apr  1 00:27:48] pmdabcc(22341) Info: Initializing, currently in 'notready' state.
    [Wed Apr  1 00:27:48] pmdabcc(22341) Info: Enabled modules:
    [Wed Apr  1 00:27:48] pmdabcc(22341) Info: ['biolatency', 'sysfork',
    [...]
    Updating the Performance Metrics Name Space (PMNS) ...
    Terminate PMDA if already installed ...
    Updating the PMCD control file, and notifying PMCD ...
    Check bcc metrics have appeared ... 1 warnings, 1 metrics and 0 values
    Copy to Clipboard Toggle word wrap

11.13. Viewing the PCP Vector Checklist

The PCP Vector data source displays live metrics and uses the pcp metrics. It analyzes data for individual hosts.

After adding the PCP Vector data source, you can view the dashboard with an overview of useful metrics and view the related troubleshooting or reference links in the checklist.

Prerequisites

Procedure

  1. Log into the Grafana web UI.
  2. In the menu, navigate to Connections Data sources + Add new data source.
  3. In the Add data source pane, type vector in the Filter by name or type text box and then click PCP Vector.
  4. In the Data Sources / pcp-vector-datasource pane, perform the following:

    1. Add http://localhost:44322 in the URL field and then click Save & Test.
    2. Click Dashboards tab Import PCP Vector: Host Overview to see a dashboard with an overview of any useful metrics.

      Figure 11.8. PCP Vector: Host Overview

  5. In the menu, navigate to Apps Performance Co-Pilot PCP Vector Checklist.

    In the PCP checklist, click the question mark icon pcp vector checklist troubleshooting doc for help or the warning icon pcp vector checklist warning to view the related troubleshooting or reference links.

    Figure 11.9. Performance Co-Pilot / PCP Vector Checklist

11.14. Using heatmaps in Grafana

You can use heatmaps in Grafana to view histograms of your data over time, identify trends and patterns in your data, and see how they change over time. Each column within a heatmap represents a single histogram with different colored cells representing the different densities of observation of a given value within that histogram.

Important

This specific workflow is for the heatmaps in Grafana version 10 and later on RHEL9.

Prerequisites

Procedure

  1. In the menu, select Dashboards New Dashboard + Add visualization.
  2. In the Select data source pane, select pcp-redis-datasource.
  3. In the Query tab, in the text field below A, enter a metric, for example, kernel.all.load to visualize the kernel load graph.
  4. From the Time series drop-down menu on the right, select Heatmap.
  5. Optional: In the Panel Options dropdown menu, add a Panel Title and Description.
  6. In the Heatmap dropdown menu, under the Calculate from data setting, click Yes.

    Heatmap

    A configured Grafana heatmap

  7. Optional: In the Colors dropdown menu, change the Scheme from the default Orange and select the number of steps (color shades).
  8. Optional: In the Tooltip dropdown menu, click the toggle to display a cell’s position within its specific histogram when hovering your cursor over a cell in the heatmap. For example:

    Show histogram (Y Axis) cell display

    A cell’s specific position within its histogram

11.15. Managing SELinux booleans for Grafana

The grafana-selinux subpackage includes several SELinux booleans that control Grafana’s access to external services. These booleans are off by default. You can turn them on or off based on your system requirements.

Prerequisites

  • You have installed grafana-selinux subpackage.
  • You have root privileges.

Procedure

  1. View all Grafana-related SELinux booleans:

    # semanage boolean -l | grep grafana
    Copy to Clipboard Toggle word wrap
  2. Enable a SELinux boolean:

    # setsebool [-P] <boolean_name> on
    Copy to Clipboard Toggle word wrap
    • Replace <boolean_name> with the name of the SELinux boolean you want to enable.
    • Use the -P option to make the change persistent across system reboots.
  3. Optional: Turn off any SELinux option:

    # setsebool [-P] <boolean_name> off
    Copy to Clipboard Toggle word wrap

11.16. Troubleshooting Grafana issues

It is sometimes neccesary to troubleshoot Grafana issues, such as, Grafana does not display any data, the dashboard is black, or similar issues.

Procedure

  • Verify that the pmlogger service is up and running by executing the following command:

    $ systemctl status pmlogger
    Copy to Clipboard Toggle word wrap
  • Verify if files were created or modified to the disk by executing the following command:

    $ ls /var/log/pcp/pmlogger/$(hostname)/ -rlt
    total 4024
    -rw-r--r--. 1 pcp pcp   45996 Oct 13  2019 20191013.20.07.meta.xz
    -rw-r--r--. 1 pcp pcp     412 Oct 13  2019 20191013.20.07.index
    -rw-r--r--. 1 pcp pcp   32188 Oct 13  2019 20191013.20.07.0.xz
    -rw-r--r--. 1 pcp pcp   44756 Oct 13  2019 20191013.20.30-00.meta.xz
    [..]
    Copy to Clipboard Toggle word wrap
  • Verify that the pmproxy service is running by executing the following command:

    $ systemctl status pmproxy
    Copy to Clipboard Toggle word wrap
  • Verify that pmproxy is running, time series support is enabled, and a connection to Redis is established by viewing the /var/log/pcp/pmproxy/pmproxy.log file and ensure that it contains the following text:

    pmproxy(1716) Info: Redis slots, command keys, schema version setup
    Copy to Clipboard Toggle word wrap

    Here, 1716 is the PID of pmproxy, which will be different for every invocation of pmproxy.

  • Verify if the Redis database contains any keys by executing the following command:

    $ redis-cli dbsize
    (integer) 34837
    Copy to Clipboard Toggle word wrap
  • Verify if any PCP metrics are in the Redis database and pmproxy is able to access them by executing the following commands:

    $ pmseries disk.dev.read
    2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
    
    $ pmseries "disk.dev.read[count:10]"
    2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
        [Mon Jul 26 12:21:10.085468000 2021] 117971 70e83e88d4e1857a3a31605c6d1333755f2dd17c
        [Mon Jul 26 12:21:00.087401000 2021] 117758 70e83e88d4e1857a3a31605c6d1333755f2dd17c
        [Mon Jul 26 12:20:50.085738000 2021] 116688 70e83e88d4e1857a3a31605c6d1333755f2dd17c
    [...]
    Copy to Clipboard Toggle word wrap
    $ redis-cli --scan --pattern "*$(pmseries 'disk.dev.read')"
    
    pcp:metric.name:series:2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
    pcp:values:series:2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
    pcp:desc:series:2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
    pcp:labelvalue:series:2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
    pcp:instances:series:2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
    pcp:labelflags:series:2eb3e58d8f1e231361fb15cf1aa26fe534b4d9df
    Copy to Clipboard Toggle word wrap
  • Verify if there are any errors in the Grafana logs by executing the following command:

    $ journalctl -e -u grafana-server
    -- Logs begin at Mon 2021-07-26 11:55:10 IST, end at Mon 2021-07-26 12:30:15 IST. --
    Jul 26 11:55:17 localhost.localdomain systemd[1]: Starting Grafana instance...
    Jul 26 11:55:17 localhost.localdomain grafana-server[1171]: t=2021-07-26T11:55:17+0530 lvl=info msg="Starting Grafana" logger=server version=7.3.6 c>
    Jul 26 11:55:17 localhost.localdomain grafana-server[1171]: t=2021-07-26T11:55:17+0530 lvl=info msg="Config loaded from" logger=settings file=/usr/s>
    Jul 26 11:55:17 localhost.localdomain grafana-server[1171]: t=2021-07-26T11:55:17+0530 lvl=info msg="Config loaded from" logger=settings file=/etc/g>
    [...]
    Copy to Clipboard Toggle word wrap
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat