Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

example: add Docker Compose example #178

Merged
merged 3 commits into from
Apr 12, 2024
Merged

example: add Docker Compose example #178

merged 3 commits into from
Apr 12, 2024

Conversation

rfratto
Copy link
Member

@rfratto rfratto commented Apr 11, 2024

This commit adds a new Docker Compose example for users to quickly test running Alloy either in a Docker container or locally, sending data to databases in a Docker container.

By default, the following are deployed:

  • Visualization

    • Grafana 10.1.9
    • A one-shot container to deploy the Alloy mixin to Grafana
    • A container which watches the Alloy mixin folder and deploys changes automatically
  • Databases

    • Mimir 2.12.0
    • Loki 3.0.0
    • Tempo 2.4.1
    • Pyroscope 1.5.0

Grafana Alloy can also be deployed by passing the --profile=alloy command to Docker Compose when starting and stopping:

docker compose --profile=alloy up -d
docker compose --profile=alloy down

Alternatively, Alloy can be run locally using the config file in example/config/alloy/config.alloy.

The default Alloy configuration used in the Docker Compose environment configures Alloy to self-collect metrics, logs, traces, and profiles, and send them to the backend databases.

This commit adds a new Docker Compose example for users to quickly test
running Alloy either in a Docker container or locally, sending data to
databases in a Docker container.

By default, the following are deployed:

* Visualization
  * Grafana 10.1.9
  * A one-shot container to deploy the Alloy mixin to Grafana
  * A container which watches the Alloy mixin folder and deploys changes
    automatically

* Databases
  * Mimir 2.12.0
  * Loki 3.0.0
  * Tempo 2.4.1
  * Pyroscope 1.5.0

Grafana Alloy can also be deployed by passing the `--profile=alloy`
command to Docker Compose when starting and stopping:

```
docker compose --profile=alloy up -d
```

```
docker compose --profile=alloy down
```

Alternatively, Alloy can be run locally using the config file in
example/config/alloy/config.alloy.

The default Alloy configuration used in the Docker Compose environment
configures Alloy to self-collect metrics, logs, traces, and profiles,
and send them to the backend databases.
@rfratto rfratto force-pushed the docker-compose-example branch from 47f1e28 to 0644ce8 Compare April 11, 2024 16:51
Copy link
Contributor

@wildum wildum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM besides the mistake in the doc

example/README.md Outdated Show resolved Hide resolved
Co-authored-by: William Dumont <[email protected]>
@rfratto rfratto merged commit ff26c95 into main Apr 12, 2024
10 checks passed
@rfratto rfratto deleted the docker-compose-example branch April 12, 2024 13:27
@rfratto rfratto added the backport-to-agent:no PR should NOT be backported to the agent repo. label Apr 23, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport-to-agent:no PR should NOT be backported to the agent repo. frozen-due-to-age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants