Discussion on Clickhouse Query Timestamp Interpretation
TLDR Sumanth asked for clarification about timestamp interpretation in a Clickhouse query and its relation to service delay. Srikanth explained it as the start time, but Sumanth expressed doubts.
Oct 19, 2023 (1 month ago)
consider the following output from executing a clickhouse query on clickhouse-client shell
┌─────────────────────timestamp─┬─traceID──────────────────────────┬─serviceName──────────┬─name──────────────────────────────────┬─durationNano─┐ │ 2023-10-18 06:31:22.013556377 │ 5d12acb2b83f6f3d68c998377c873d5f │ Prod-PostNlpNotifier │ GET │ 46539987 │ │ 2023-10-18 06:31:22.060526394 │ 5d12acb2b83f6f3d68c998377c873d5f │ Prod-PostNlpNotifier │ PUT │ 76430081 │ │ 2023-10-18 06:31:22.013369223 │ 5d12acb2b83f6f3d68c998377c873d5f │ Prod-PostNlpNotifier │ webhook-post-nlp-notifier-alt process │ 123598772 │
There are the entries for traceID 5d12acb2b83f6f3d68c998377c873d5f from serviceName Prod-PostNlpNotifier
1. The value for timestamp. What does that indicate? does that indicate when the trace first encountered prod-postnlpnotifier?
a. Does that mean to get the timestamp for when the trace is exiting the service is to do timestamp+durationNano ?
SELECT timestamp, traceID, serviceName, durationNano FROM signoz_traces.distributed_signoz_index_v2 WHERE (traceID IN ('5d12acb2b83f6f3d68c998377c873d5f')) AND (serviceName IN ('Prod-ingestion-wh-consumer', 'Prod-PostNlpNotifier'))
hence the question
would be 10mins max, only 1 question
Indexed 1023 threads (61% resolved)
Services UI Goes Blank Due to Retention Issue with S3 Bucket
oluchi reports issue with services UI going blank after a while. Conversation explores possible reasons, such as S3 connection problems and disk space, but no resolution is reached.
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.
Incorrect Alert Firing Issue in Threshold Condition
Harshith.R.S is experiencing an issue with alerts firing when the value is above the threshold. The issue remains unresolved after trying different query modifications suggested by Amol.
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.
Clickhouse Query Timeout in SigNoz Dashboard
Daniel experienced query timeouts in SigNoz dashboard. vishal-signoz confirmed it's a non-configurable 60s limit, but created a GitHub issue for adding the feature.