https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
a
cc: @nitya-signoz
n
Can you share the configuration? Also if your fields are loaded but not visible in the UI there might be issues with timestamp. Can you run the commands and share output
Copy code
kubectl exec -n platform -it chi-my-release-clickhouse-cluster-0-0-0 -- sh

clickhouse client

use signoz_logs;

select timestamp,observed_timestamp from distributed_logs order by timestamp desc limit 10;
m
Copy code
┌───────────timestamp─┬──observed_timestamp─┐
│ 1677577033101391005 │ 1677577033114197754 │
│ 1677577033087210293 │ 1677577033114149167 │
│ 1677577033081940586 │ 1677577033113942963 │
│ 1677577033079232086 │ 1677577033114117714 │
│ 1677577033074985781 │ 1677577033114088974 │
│ 1677577033071399878 │ 1677577033113746096 │
│ 1677577033068867909 │ 1677577033114495821 │
│ 1677577033058288277 │ 1677577033114040042 │
│ 1677577033054256687 │ 1677577033114446222 │
│ 1677577033036741379 │ 1677577033114394174 │
└─────────────────────┴─────────────────────┘
here you go
n
interesting, can you share the API response of 
/logs
endpoint from the network tab?
Along with the request params ^
m
There is no request with 
/logs
only 
aggregate
n
What version of SigNoz are you using?
@Palash Gupta can there be a case where /logs is not triggered on the UI ?
m
v0.16.0
Oh found some after a page refresh
Copy code
{
  "status": "error",
  "data": "Failed to fetch logs from the DB",
  "errorType": "internal",
  "error": "code: 241, message: Memory limit (total) exceeded: would use 3.62 GiB (attempt to allocate chunk of 5064994 bytes), maximum: 3.60 GiB. OvercommitTracker decision: Query was selected to stop by OvercommitTracker.: (while reading column attributes_string_value): While executing MergeTreeReverse"
}
here is the clickhouse resources
Copy code
resources:
        requests:
          cpu: 100m
          memory: 200Mi
        limits:
          cpu: 2000m
          memory: 4Gi
I should increase resources? or there are other settings?
n
Yeah please increase the resources and try it out first. There are issues about this on clickhouse https://github.com/ClickHouse/ClickHouse/issues/17631 . But you can start by doubling up the resources and trying it out.
p
can there be a case where /logs is not triggered on the UI ?
I am not aware of such case... @Muhammed Hussein Karimi can you please share the loom video for the same
m
Fixed by increasing the memory limits
p
oh great ... @nitya-signoz can we update same in the docs
11 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by