TLDR Harald faced a missing log issue and discovered that logs appeared once the pod was ready. Updating SigNoz and adding more RAM to the k8s cluster fixed the issue.
This is giving me nuts again :disappointed: I don't know what I am doing wrong... Logs - in general work. But where is this one specific log?
Do I need to wait? Do I need to press the Go live?
omg :disappointed: is it my browser v
$ date Fri Mar 17 20:22:23 CET 2023 (localtime on my desktop)
$ date Fri Mar 17 19:22:15 UTC 2023 (localtime on my k8s cluster)
is it this?
If you doing search on body along with filtering queries please use fulltext
‘id IN ('2DCVZOsKHioCeuvbObzVzzL1eZ5') AND fulltext contains 'Dispatch Successful'’
Ok I found it out :slightly_smiling_face:
I have a feeling that a pod - at least - must have a Ready status, before we get logs.
I can't prove it - but waiting until the pod is ready did the trick.
Okay so you are saying that logs are not ingested to SigNoz unless the pod is in ready state ?
I now "fixed" it by just 1) add more ram to k8s 2) update SigNoz to the latest version
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