Troubleshooting Signoz Server Syslog Receiver Issue
TLDR Jun had issues with syslog receiver on Signoz server. After suggestions from nitya-signoz and Hannes, and modifying IP settings on docker-compose.yaml, problem was resolved.
Aug 24, 2023 (1 month ago)
However, I do not see any ports opened on the Signoz server when i do a netstat, is anyone able to confirm if the user guide is correct? Or if there are any error logs I can look at?
I'm unsure if these logs are helpful but if you or any others are able to take a look, that would be great!
Aug 25, 2023 (1 month ago)
And on the otel-collector-config.yaml, I have configrued a syslog receiver along with adding that receiver under the service section
Indexed 825 threads (61% resolved)
Docker-Compose YAML File for Sending Syslog Logs to Signoz
David asked for a signoz saas setup example docker-compose yaml file for syslog logs. Srikanth recommended using otel-collector-contrib binary/container, configured with signoz API key.
Removing Default Logs and Collecting Application Logs
Srikanth wanted to remove default logs and collect their application logs. nitya-signoz provided two solutions, and Srikanth chose the second one, which involves editing the ote-collector-config.yaml file.
Configuring OTel Collector to Export Data to SigNoz
James asked how to configure the otel collector to send data to SigNoz. Ankit suggested using the otlp exporter in the collector configuration. James found that SigNoz uses its own otel collector and adjusted the port bindings accordingly.
Issues with Transmitting Logs from Logstash to Signoz
Krishnadas struggled to transmit logs from Logstash to Signoz. After a rich dialogue with Prashant and nitya-signoz, the issue was resolved when Krishnadas removed the existing docker container logs receiver and added the filelog receiver for their logs folder.
SigNoz Deployment Issue in Docker Swarm with NFS Share
sati encounters issues with setting up SigNoz in docker-swarm with an NFS share resulting in otel-collector crash and inaccessible GUI. Nick experienced a similar problem and shared a workaround.