Skip to main content

Install the agent on a static server

Sending system information to Experience Monitoring requires installing the Experience Monitoring agent on all servers you wish to monitor.

  • The agent is only compatible with Linux.
  • This procedure can be used directly if your application or site is hosted on a static server. For autoscaling environments (including Docker), it must be adapted to manage the hostid correctly. See Install the agent in autoscaling environments.

Compatibility​

  • Debian 10, 11, 12
  • Ubuntu Jammy, Kinetic, Lunar
  • CentOS 7, CentOS 8 Stream

Prerequisites​

  • To install the Experience Monitoring agent, you will need an auto-registration token. Each site has its own token. To retrieve a token, in the site you want, go to Settings > System. The token is displayed in a green box.

  • System agents must be able to communicate with our infrastructure. You may need to whitelist our IP addresses.

  • To add, modify, or delete a server in Experience Monitoring, you must have Admin or Owner permissions on your organization. Ask your administrator or support to grant you the correct rights.

Installation procedure​

  1. Add the following line to the /etc/apt/sources.list.d/quanta.list file.

    deb [signed-by=/usr/share/keyrings/quanta-archive-keyring.pgp] http://apt.quanta.io/debian buster main

    If unsure of your version of Debian, you can read the /etc/debian_version file.

  2. Download and add the GPG key for our repository:

    curl https://apt.quanta.io/quanta-repo-key.gpg | gpg -o /usr/share/keyrings/quanta-archive-keyring.pgp --dearmor

  3. Update the package list:

    apt update

  4. Install the agent:

    apt install quanta-agent

    You will be prompted for the token during installation, and system data should appear in Experience Monitoring within a minute. You can then install application agents if you need them.

Troubleshooting agent installation​

I don't see data coming in, where can I find information to troubleshoot?

The agent uses syslog for logging; you will generally find logs in /var/log/daemon.log or /var/log/syslog. If you can't find the source of the error, please contact Centreon support.

You can send logs to another file by changing the file variable under the logger section in /etc/quanta/agent.yml (make sure to set up log rotation).

Modifying an existing installation​

If you want to modify the configuration of an Experience Monitoring agent that is already installed on one of your servers, you will find its configuration in the /etc/quanta/agent.yml file. It contains the main connection information, including the Experience Monitoring token corresponding to the relevant site. Access to this file can be useful if you monitor multiple sites with the same Experience Monitoring account and wish to specify the correct token to associate each server with its hosted site (e.g., for separate production and pre-production servers).

Here is an excerpt from the /etc/quanta/agent.yml file:

user: quanta-agent
directory: /var/run/quanta
pidfile: /var/run/quanta/agent.pid
daemonize: yes

poll_interval: 60
update_interval: 15

logger:
  level: notice
  file: syslog

hostid: [...] <- server ID, automatically generated at installation
quanta_token: [...] <- insert here the token corresponding to your site

[...]

Endpoint addresses for server agents​

If you use the Experience Monitoring agent, each of your servers regularly sends data (once per minute) to the Experience Monitoring service.

This is outbound HTTPS traffic (port 443) and is often allowed by default. However, if your firewall rules are strict and you need to allow specific destinations for Experience Monitoring, list the following destination IP addresses:

  • 52.215.166.110
  • 52.215.179.235
  • 52.215.180.115