Troubleshooting | Grafana Labs
grafana.com › docs › tempoThey walk you through debugging each part of the ingestion and query pipeline to drill down and diagnose issues. Sending traces. Spans are being refused with “pusher failed to consume trace data” Is the Grafana Agent sending to the backend; Querying. I am unable to find my traces in Tempo; I am getting error message “Too many jobs in the queue”
Troubleshooting | Grafana Labs
grafana.com › docs › grafanaTroubleshoot with logs. If you encounter an error or problem, then you can check the Grafana server log. Usually located at /var/log/grafana/grafana.log on Unix systems or in <grafana_install_dir>/data/log on other platforms and manual installations. You can enable more logging by changing log level in the Grafana configuration file.
Grafana Issues a Security Patch After an Exploit for CVE-2021 ...
www.deepwatch.com › labs › customer-advisory-forDec 09, 2021 · After security researchers released proof-of-concept code to exploit the issue over the weekend, Grafana Labs issued an emergency security update today to patch a critical vulnerability in its flagship product self-hosted Grafana dashboard versions from v8.0.0-beta1 through v8.3.0. The flaw, tracked as CVE-2021-43798, is a directory traversal attack that allows a threat actor to read files outside the Grafana application’s folder, such as password and configuration files.