SigNoz Frontend Container_ID Leak Issue
TLDR Cheslav reported an issue with the SigNoz frontend leaking container_ids. nitya-signoz suggested ways to obtain logs and check the issue.
Apr 08, 2023 (8 months ago)
Cheslav
09:33 AMcontainer_id is multiplied more and more....
Pranay
03:58 PM
nitya-signoz
05:11 PMCan you also share the API request and response of
/logs endpoint by opening the network tab?Cheslav
06:50 PMI just was trying to filter all log entries of SigNoz out by querying 'container_id NIN ...' when it started to leak. I were putting every container_id into list on and on. First the field container_id was duplicated in the filter and into every log entry. Then it started to leak.
Cheslav
06:50 PMApr 10, 2023 (8 months ago)
nitya-signoz
11:37 AM
SigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Removing SigNoz's Own Logs from Dashboard
Geoffrey wanted to remove SigNoz's own logs from the dashboard. nitya-signoz provided a solution referencing an existing issue and a filter for ingesting only desired logs.
Troubleshooting SigNoz Monitoring for AWS EC2 Docker-Compose Application
dipak has problems with SigNoz integration to monitor containers in an AWS EC2 Docker-Compose application. Prashant suggests updating the dashboard and using different guides for log collection, metrics collection and application instrumentation. Issues are still unresolved.
Signoz Frontend Login Issues on AWS EC2
Jose has an issue with the Signoz frontend after deploying it to an AWS EC2 instance. Prashant suspects a problem with Nginx and query-service IPs and provided a solution to verify the issue.