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

feat: add opentelemetry example for alloy #53

Merged
merged 7 commits into from
Oct 11, 2024
Merged

Conversation

sunng87
Copy link
Member

@sunng87 sunng87 commented Oct 7, 2024

This patch reuse alloy example to demo opentelemetry data ingestion.

For more information, see the README.

@sunng87 sunng87 requested a review from daviderli614 October 7, 2024 23:47
@daviderli614
Copy link
Member

I tried to run the demo and got an error:

git clone https://github.com/GreptimeTeam/demo-scene.git
cd demo-scene/grafana-alloy
docker compose up
services.envsubst.env_file.0 must be a string

image

@sunng87
Copy link
Member Author

sunng87 commented Oct 9, 2024

@daviderli614 according to https://docs.docker.com/compose/how-tos/environment-variables/set-environment-variables/#additional-information-1, it requires a minimal version of docker compose. I will add to readme.

called `prometheus.exporter.unix` and export the data to both a Prometheus
remote write sink and an OpenTelemetry-compatible collector, which is
GreptimeDB.

## Run in GreptimeCloud

By default, this example writes data into a GreptimeDB instance within the
docker compose. It's also possible to write to your own GreptimeCloud instance
by creating a `greptime.env` file from our sample `greptime.env.sample` and
Copy link
Member

@daviderli614 daviderli614 Oct 9, 2024

Choose a reason for hiding this comment

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

Added a link to greptime.env.sample, it looks like: [greptime.env.sample](./greptime.env.sample) ?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think it's ok. The idea is to let user copy the sample and rename

@sunng87 sunng87 requested a review from dedlockdave October 9, 2024 17:32
@sunng87
Copy link
Member Author

sunng87 commented Oct 9, 2024

@dedlockdave I was going to invite David but Li Yang's id was quite similar @daviderli614. Thank you for reviewing this and it has been quite helpful.

@dedlockdave dedlockdave merged commit c2c5e1c into main Oct 11, 2024
1 check passed
@dedlockdave dedlockdave deleted the feature/otel-alloy branch October 11, 2024 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants