Skip to main content
This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
This feature isn’t available to all Chronosphere Telemetry Pipeline users. For more information, contact Chronosphere Support.
In Chronosphere Telemetry Pipeline, you can use fleets to manage instances of Core Agent. Use this guide to install Core Agent on Debian-based Linux distributions.

​
Supported environments

Core Agent supports the following Debian-based distributions and architectures:

​
Dependencies

For Debian-based installations, Core Agent has the following general dependencies:
  • libc
  • libsasl
  • libsystemd
  • libyaml
  • OpenSSL
  • zlib
To retrieve a list of specific dependencies for your environment, run the following command:
Replace PACKAGE with the name of the Core Agent package.

​
Validate packages

When retrieving packages from the Core Agent repository, Chronosphere uses dual validation (SHA256) and a GPG key.

​
SHA256 check

The SHA256 file is distributed as the files.sha256 file in the Core Agent repository. This file contains a list of all included packages.

​
Verify signatures

Core Agent packages are signed with calyptia.key. You can use dpkg and apt-key to verify these signatures.
Replace PACKAGE with the name of the Core Agent package.

​
Install

Use these steps to install and enable Core Agent:
  1. Run the following command to update your APT package list:
  2. Run the following command to upgrade your APT packages:
  3. Run the following command to install Core Agent:
  4. Run the following command to instruct systemd to enable the Core Agent service:
  5. Perform a status check to confirm Core Agent is active. The status check should return output similar to the following:
    The default configuration of Core Agent is to collect metrics of CPU usage and send those metrics to stdout. You can see this outgoing data in your /var/log/messages file.