-
Notifications
You must be signed in to change notification settings - Fork 68
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
Documentation for shipping server logs/metrics via alloy #77
Comments
Hey there @josegonzalez, thanks for reaching out! 👋 We have a similar tutorial here: https://grafana.com/docs/alloy/latest/collect/opentelemetry-to-lgtm-stack/ Could you take a look and see if it answers your question? |
Somewhat? It's not super clear how to grab the actual log data (or even stuff like server metrics) to ship over, or if alloy is even the correct way. I only point at Alloy as the grafana agent is deprecated in favor of it. |
Hi, I've found the docs helpful, but they seem to tackle different specific hello-world-esque use cases. I have been reading through the Collect Kubernetes logs documentation, which demonstrates how to do so with Loki components. This is also the recommended way of retrieving logs from infrastructure per the Choose a component page. However, these guides fall flat as only an OTEL collector for GRPC and HTTP is exposed in otel-lgtm container. I've played around, trying to forward Loki logs to the otel-lgtm docker container, thinking that the HTTP OTEL endpoint might serve I get the feeling that we may be able to do the following;
It would be great to know which of these means of ingesting Loki logs is preferred, and perhaps a brief note in the README of this project would go down a treat to help inform people moving forwards! :-) |
Once this is setup, there is an OTLP endpoint for collecting logs/metrics. That said, there isn't really an end-to-end setup for how to configure this with Alloy. Would it be possible for someone to write a short tutorial on how to do that?
The text was updated successfully, but these errors were encountered: