Understanding Host Metrics Graph and Memory Usage Rate
TLDR Div needed help understanding a host metrics graph and had issues with memory usage rate. Srikanth guided them to correct the legend format and advised against using rate on gauge metric.
1
1
Apr 05, 2023 (6 months ago)
Div
08:27 AM1
Div
08:28 AMAnkit
08:29 AMcc: Ashu
1
Srikanth
08:33 AMDiv
08:33 AMSrikanth
08:34 AM{{state}}
like you did for the first query. Otherwise it doesn’t know what to format and shows the query nameDiv
08:35 AMA
and only displaying the Formula 👍Div
08:35 AMDiv
08:37 AMprocess_memory_rss
its Rate_avg and in kilobyte, showing the values in negative as well, is this normal ?
Srikanth
08:45 AMDiv
08:49 AMwe are using otel host metrics on our service to pass this data to Signoz, similary how we are sending the cpu and memory metrics
Srikanth
09:35 AMDiv
09:39 AMDiv
09:42 AMSigNoz Community
Indexed 826 threads (62% resolved)
Similar Threads
Troubleshooting Kubernetes Metrics in SigNoz Dashboard
kmpartner is experiencing issues displaying all metrics in the kubernetes-metrics dashboard. vishal-signoz shared a link to sigNoz tutorial and has requested assistance from Prashant.
Issues with SigNoz Setup and Data Persistence in AKS
Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.
Troubleshooting k8s-metrics Dashboards in SigNoz v0.19.0
kmpartner encountered issues displaying k8s-metrics dashboards in SigNoz, while hostmetrics-k8s.json mostly works. Srikanth suggested checking SigNoz's documentation for a solution.
Discrepancy in RAM Usage Metrics in Signoz vs. Kubectl
Shravan observes a discrepancy between Signoz and kubectl RAM usage metrics. Srikanth acknowledges the issue and directs them to create a GitHub issue.
Integrating TimescaleDB Prometheus Data with SigNoz
Milan was unable to view TimescaleDB Prometheus data in SigNoz. With suggestions from Srikanth and Prashant, they identified and fixed a configuration error by removing the unnecessary evaluation_interval setting.