Deploying otel+signoz on EC2: Recommended Architecture Pattern
TLDR Agustin sought advice on deploying otel+signoz on EC2. Both Srikanth and Alexei suggested option 1, with Alexei also referencing otel docs for further information on deployment before Agustin closed the thread.
1
1
Aug 10, 2023 (3 months ago)
Agustin
03:47 PM1. Each EC2 instance has an otel collector that fowards the data to signoz otel-collector
2. Each EC2 instance has an otel collector that fowards the data directly to the clickhouse DB
3. The signoz otel-collector scraps the data from each EC2 instance’s otel collector
4. The signoz otel-collector scraps the data directly form eachh EC2 instance receiver (prometheus, jaeger, etc)
Im guessing 3 and 4 would require some sort of service discovery
Srikanth
03:59 PMAlexei
06:41 PM1
Alexei
06:44 PM1
Agustin
06:51 PMAgustin
06:52 PMSigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Integrating Otel Collector Agent with Signoz on ECS
Div asks how to integrate an otel collector agent for their microservices on ECS with Signoz. Srikanth suggests running it as a separate container or a background process, and shares a relevant document.
SigNoz Deployment and Collector Concerns in Multi-Cluster Application
Romil asks about deploying k8s-infra chart and collector roles in a multi-cluster setup. Ankit recommends deploying k8s-infra chart for each cluster, and mentions the importance of using SigNoz's otel-collector for their data schema.
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.