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

Incorrect (agent-centric) troubleshooting guidance #688

Open
Eve832 opened this issue Apr 26, 2024 · 3 comments
Open

Incorrect (agent-centric) troubleshooting guidance #688

Eve832 opened this issue Apr 26, 2024 · 3 comments
Assignees
Labels
needs-attention type/docs Docs Squad label across all Grafana Labs repos

Comments

@Eve832
Copy link
Contributor

Eve832 commented Apr 26, 2024

URL

https://grafana.com/docs/grafana-cloud/monitor-infrastructure/integrations/install-troubleshoot-linux/#no-metrics-were-found-for-this-integration

Feedback

Gaurav Soni has found that a troubleshooting command did not help him address a customer concern, likely because it hasn't been updated for the linux integration which now uses Alloy.
slack link: https://raintank-corp.slack.com/archives/C5PG2JK8W/p1714138195021599

Post:

While troubleshooting Alloy configuration and following troubleshooting guidance:
https://grafana.com/docs/grafana-cloud/monitor-infrastructure/integrations/install-troubleshoot-linux/#no-metrics-were-found-for-this-integration
it seems to give me a wrong command[probably old as UI recommend using Alloy now]:

admin@ip-172-31-29-110:~/alloy$ journalctl -u grafana-agent.service -n 100 --no-pager
-- No entries --
This command resulted in no journal entries being shown.
I expected that following troubleshooting guidance would give me helpful diagnostic information.
Here's what gave me useful information:
admin@ip-172-31-29-110:~/alloy$ journalctl -u alloy -n 100 --no-pager
Apr 26 13:04:33 ip-172-31-29-110 systemd[1]: Started alloy.service - Vendor-agnostic OpenTelemetry Collector distribution with programmable pipelines.
Apr 26 13:04:33 ip-172-31-29-110 alloy[703]: ts=2024-04-26T13:04:33.665498496Z level=info "boringcrypto enabled"=false
...
...

Can we get the doc updated? (edited)

@Eve832 Eve832 added the type/docs Docs Squad label across all Grafana Labs repos label Apr 26, 2024
@clayton-cornell
Copy link
Contributor

Integrations team has this on their ToDo list and updates are pending.

Copy link
Contributor

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!

@clayton-cornell
Copy link
Contributor

Looks like this has received an update now... https://grafana.com/docs/grafana-cloud/monitor-infrastructure/integrations/troubleshoot/install-troubleshoot-linux-alloy/ is the new URL

@grvsoni does this cover what you were asking for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-attention type/docs Docs Squad label across all Grafana Labs repos
Projects
None yet
Development

No branches or pull requests

2 participants