Splunk Cloud - logs: errors or debugs #212
Replies: 1 comment
-
@brunoongaratto I believe you might have the wrong discussion board for your question as this is Observability workshops. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Morning guys,
I'm making a dashboard on Splunk Cloud to monitor errors through the Argo Events logs.
When I created a filter to show errors referring to "eventbus", the 4 errors below are returning:
log: [7] 2023/08/30 00:31:26.167405 [DBG] 244.17.11.196:33848 - cid:166 - Client Ping Timer
log: [7] 2023/08/30 00:31:24.284655 [DBG] 244.17.1.113:39400 - cid:165 - Delaying PING due to remote client data or ping 2s ago [10:32 AM]
log: [6] 2023/08/30 00:31:15.560520 [DBG] RAFT [WIs1b7tQ - C-R3F-6hkl40wZ] Installing snapshot of 8 bytes
log: [7] 2023/08/30 00:31:16.182104 [DBG] 244.17.4.20:6222 - rid:14 - Router Ping Timer
Analysing the log, we can see the initials "[DBG]", which could be debug and not an error, but the stream is returning "stderr".
So I don't know if there is an error in the log entry or if I really consider the 4 logs above to be errors...
Has anyone analysed or gone through this situation?
Thanks,
Bruno
Beta Was this translation helpful? Give feedback.
All reactions