scalyr/scalyr-agent-docker-fips repository overview

⁠Description

Runs the Scalyr Agent in its own Docker container. Docker provides a logging framework by which Standard Output and Standard Error from all containers on the same host are gathered. The Scalyr Agent watches these logs and uploads them to the Scalyr backend, along with metrics. This image uses the Docker-recommended JSON File logging driver, not syslog. We recommend this image over scalyr-agent-docker-syslog⁠.

More info at: https://app.scalyr.com/help/install-agent-docker#dockerJSON⁠

⁠What is Scalyr Agent

The Scalyr Agent is a daemon you can install on each of your servers. It uploads logs and system metrics. This second-generation agent is easy to install and manage, with minimal dependencies and resource requirements.

⁠Image Variants

⁠scalyr-agent-docker-fips:<version>

⁠Development / Testing Images

In addition to the stable version tags (e.g. 2.1.28, 2.1.27), a new development tag is also uploaded on each push to the Github repository master branch.

Those development versions of the images are primarily meant to be used for testing and not in production environments. Image tags for those images use the following format: <image name>:<git commit sha>, e.g. scalyr-k8s-agent:45c9e691424743cb8d023a619780e578e95d555c.

⁠Current Stable Version

Information about the current stable version is available at https://github.com/scalyr/scalyr-agent-2/blob/release/VERSION⁠.

⁠Supported Architectures

The following architectures are supported

• linux/amd64
• linux/arm64 (e.g. Amazon Graviton and other ARM64 based devices)

⁠Support

Documentation and support information is available at the following links:

• https://app.scalyr.com/help⁠
• https://support.dataset.com/hc/en-us⁠

⁠Source Code

Scalyr agent is licensed under Apache 2.0 license. Agent source code is available at https://github.com/scalyr/scalyr-agent-2⁠.

⁠License

View Scalyr Agent license information⁠.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.