Hi Team, Signoz self-hosted log page is getting unresponsive, though logs are getting displayed but unable to perform any action, i suspect this happened after i implemented log pipeline and then deleted it but not sure . also i noticed multiple frames of log in UI, i see some log section just below graph signoz version : 0.67.1 please help debug this issue

cc: @nitya-signoz/@Raj Kamal can you please check this?

I see that you parsed something unwanted in severity text, I am guessing that might have resulted in a lot of values which made your system run out of memory, can you share what pipeline did you create

@nitya-signoz yes i was trying to implement log severity preprocessor for logs, after trying some configs i removed it. i was trying to parse log "body" field and categories log level by severity. i was following this doc : https://signoz.io/docs/logs-pipelines/processors/#severity-parser i did not see any pod restart due to OOM so not sure if app went out of memory. can you say how can i safely implement this and how to check if lot of values are getting created to avoid this?

Before deploying any pipeline try to simulate the pipeline to see if it’s working as expected. Also I was talking about your system/browser window memory which might have spiked up due to huge response

@nitya-signoz got it, i did try to simulate it and it did show whole message in preview, i though that was expected, now i understand preview should only show severity text extracted from original log not the whole log.