Aggregating TPS Values of Pods for Graph Display
TLDR Aditya needed to display the total TPS of multiple pods on a graph. Srikanth suggested adding a distinguishable attribute for each pod and adjusting the aggregation formula by dividing it by the interval.
May 19, 2023 (7 months ago)
May 20, 2023 (7 months ago)
You need to add pod ID to distinguish.
> I added the pod name as one of the Attribute then it showed the tps values of each pod. But i need one curve which should add the tps values of each pod and show the graph
How often are you sending the data? There will be some aggregation interval such as 60, and any aggregation you do such as SUM will perform the addition of all points falling into 60 seconds. If you need per second you need to divide by 60. You can use the query builder formula for this.
Yes and it overrides.
> How can I have signoz to aggregate values of all pods having the same timestamp_ms and fingerprint value and show me in the graph?
You can either pre-aggregate in the middle and send the aggregated data to SigNoz or send the different attributes for each pod.
> The total tps as per my logs is coming 700 per pod for 1 user. If there are 3 pods i can assume the tps is 2100. But in signoz Dashboard its showing only 700 for NOOP
If you do not provide a distinguishable attribute for each pod, the time series will be the same hence 700 instead of 2100.
> if I do SUM aggregate, it bumps the value to 50000 - 100000 which doesn’t make sense to me.
Aggregation happens over an interval of 60s. We don’t show data for each second since there won’t be enough pixels. The sum simply shows the aggregate. If you want per second at the intervals you can use the formula and divide by interval.
Indexed 1023 threads (61% resolved)
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.
Dashboard Load Issues and Possible Solutions
Al experiences dashboard loading issues since updating to `0.18.1`. Srikanth believes the issue is not version related and suggests examining queries, memory resources, and server distribution for improvements.
Troubleshooting SigNoz Auto-Instrumentation Configuration
igor is having trouble configuring auto-instrumentation for Java applications using SigNoz, with traces not appearing in the SigNoz UI. Prashant advises to check logs of the otel sidecar, use service name for endpoint, verify supported libraries, and test with telemetrygen. However, the issue still persists.