This message was deleted.
s
This message was deleted.
n
Or If your application is running in docker or k8s, then logs emitted to stdout will be collected by signoz
m
I'm in k8s and other logs are collecting except this app
I think something are wrong with my log structure
Or with my configuration
@nitya-signoz What can I do to fix that?
n
If you logs are getting printed to stdout then it will be collected, did you try to filter in the UI
m
yes
nothing shows in the SigNoz dashboard after filtering
Copy code
{
  "written_at": "2023-03-01T15:56:00.206Z",
  "written_ts": 1677686160206573000,
  "msg": "",
  "type": "log",
  "logger": "fastapi-request-logger",
  "thread": "MainThread",
  "level": "INFO",
  "module": "implementation",
  "line_no": 35,
  "span_id": "176794658234006051",
  "trace_id": "227587342002673840811008499138396058579",
  "correlation_id": "272ba70209901ac67929a2595244ce13"
}
here is the sample log
@nitya-signoz
I have removed trace_id and span_id from logs but I'm not able to see logs in signoz
@nitya-signoz
n
Can you check if by any change if the namespace where you have deployed the above application is excluded in the otel collector config file receiver ?
m
Copy code
- type: filter
              id: remove_some_logs
              expr: 'resource["k8s.namespace.name"] matches "(^stage-.*$)" and resource["k8s.namespace.name"] != "stage-this-project"'
              drop_ratio: 1.0
stage-this-project is the name of the namespace
I think this filter is not making problems
n
It shouldn’t cause any issue, but try removing it?
or if there is something else.
m
I will check But there are no other drop filters If I remove that my storage will become 100% full
n
Got it then try deploying in some other namesapce ?
m
I will test that
I changed the namespace but problem persist
@nitya-signoz
205 Views