-
Notifications
You must be signed in to change notification settings - Fork 10
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
Conversation
Co-authored-by: liyang <[email protected]>
@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 |
There was a problem hiding this comment.
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)
?
There was a problem hiding this comment.
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
@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. |
This patch reuse alloy example to demo opentelemetry data ingestion.
For more information, see the README.