TLDR Jakub inquired about adjusting time resolution and measuring latency in SigNoz. Ankit clarified that time resolution isn't adjustable and SigNoz only measures server timing, not network delays.
Hey guys, I am running SigNoz and my app in Kubernetes installed using Helm Chart,
1. how can I change the time resolution of metrics in my Dashboards, *it defaults to 1 min between points*, the same for Service tab when I click on my service, *how can I change it to something like 10-15 s between next points*? I am running performance tests and I want to observe the resource utilization and latency of my app.
Thank you in advance and hopefully someone can help me. :heart:
2. The second question is that I was testing using Locust in cluster and it was showing max latency of e.g. 1900ms while in Services in SigNoz and Traces the max time of request latency was 100ms, how does it relate to each other? I understand that SigNoz counts the latency for a service using the span duration but how does it relate to the latency shown in load testing tool?
I have also tried k6 and it was showing 500 ms latency avg while the max latency in spans of my API service was 120 ms and in Service tab p99 104ms.
Have a good day everyone :blush:
1. It is not configurable yet
2. SigNoz just measures the server timing does not take into account the network delays, queue blocks before the request reaches the application server
Thank you for your reply, so from my understanding, there is no point in scraping more often than 60s as I will not be able to see that?
Indexed 1060 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI