alloy icon indicating copy to clipboard operation
alloy copied to clipboard

Update otel to lgtm task to use grafana cloud otlp endpoints

Open erikbaranowski opened this issue 1 year ago • 5 comments

Request

https://grafana.com/docs/alloy/latest/tasks/opentelemetry-to-lgtm-stack/

Use case

When this guide was written Grafana Cloud did not have otlp endpoints for Loki and Mimir. Now that we have them we should use them!

erikbaranowski avatar Apr 11 '24 14:04 erikbaranowski

The docs at the moment talk about the LGTM stack, and AFAIK if you deploy this locally using OSS or GEM/GEL/GET then the OTEL endpoint doesn't exist.

Is it worth adding a "How to send to Grafana Cloud" section to the existing doc rather than overwriting the current content?

proffalken avatar Apr 11 '24 15:04 proffalken

It would be really lovely to get some documentation that details how to do this. For example, when I login to Grafana Cloud, the example configuration for Loki only includes a loki.write stanza for Grafana Cloud, not an OTel Loki Receiver + sending that through the Grafana Cloud OTLP exporter. Same for Prometheus.

My tracing pipeline is OTel receiver > memory limiter -> batch -> OTLP exporter, and then Loki and Prometheus for logs and metrics through their respective loki.write and prometheus.remote_write. I assume it's mostly a matter of changing it so the OTel receiver and the processors pass through metrics and logs to eventually otelcol.exporter.otlp.<name>.input, and have loki.source.* and prometheus.scrape.* forward_to into the memory processor. Having a complete example in the docs would be great.

daenney avatar Apr 13 '24 14:04 daenney

https://gist.github.com/proffalken/ac9933d92c92432bae6be4bf705a302e has two example configs, one for storing the Auth details in the config file, the second shows how to retrieve them from hashicorp vault using the new Vault integration.

I'll try to get something like this into the docs next week.

proffalken avatar Apr 13 '24 18:04 proffalken

This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it. If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue. The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity. Thank you for your contributions!

github-actions[bot] avatar May 14 '24 00:05 github-actions[bot]

Mea culpa, I completely forgot about this.

I'll try and get to this soon.

proffalken avatar May 14 '24 06:05 proffalken