#support

Multi-Destination Export with OTEL Collector and SigNoz

TLDR Alex wants to export telemetry to multiple services. Srikanth suggests using OTEL collector to forward data to both SigNoz and DataDog.

9mo

Join the chat

Mar 01, 2023 (9 months ago)

Photo of md5-270ece168a4c7dc4f8cbe53af4ddbd4f

Alex

01:06 PM

Given that there is no way to use the datadog exporter with the signoz otel collector, would it be possible to disable the OTEL collector entirely within the signoz helm chart, and only install the query service, front-end, clickhouse and alert manager? and let an external otel collector provide the actual telemetry? I need to export my traces and metrics to both services.

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

03:51 PM

You can configure the SDK to send to multiple destinations.

Alex

04:09 PM

how?

04:09

Alex

04:09 PM

you mean the OTEL SDK?

04:10

Alex

04:10 PM

that doesn't help with host metrics, or services deployed from third party images

Mar 02, 2023 (9 months ago)

Srikanth

12:22 AM

Yes, I meant OTEL SDK. I am not I follow that doesn’t help with host metrics, or services deployed from third party images. There is also another of way sending data to “agent” collector of the upstream binary/image in your services which will send data to multiple destinations.

Mar 03, 2023 (9 months ago)

Alex

09:26 AM

ok, so what you're suggesting is that SignOz acts as a hub which collects host metrics, along with application traces and metrics, and sends them to yet another collector which then exports them to the target 3rd party service?

09:34

Alex

09:34 AM

what I meant by 3rd party images is, for example, ingress-nginx which can only send to one OTLP endpoint, so that endpoint must be capable of forwarding the traces and metrics to all the services I want to send my telemetry to

Srikanth

05:27 PM

The hub can be otel collector which receives the data from applications which can then forward the data to multiple destinations.

Alex

05:40 PM

if you're talking about signoz acting as the hub, it cannot forward to the Datadog service because it doesn't contain the datadog exporter, unlike the otel-collector-contrib image which the agents run on

Srikanth

05:41 PM

I am not talking about signoz as hub but as a destination for which is why I mentioned The hub can be otel collector which receives and forwards data to multiple destination i.e both SigNoz and Datadog

Alex

05:42 PM

ok, so app -> otel collector -> signoz?

Srikanth

05:42 PM

Yes, that otel collector (contrib image) can send data to SigNoz and DataDog

Alex

05:43 PM

ok, though that means I would be running two daemonsets collecting host metrics, and one pointless collector (courtesy of the signoz helm chart)

05:43

Alex

05:43 PM

instead of just exporting data from otel collector directly to clickhouse

05:44

Alex

05:44 PM

I need to run, but I'll read your responses later

Mar 13, 2023 (9 months ago)

Alex

11:33 AM

I think I understood something wrong initially. I was able to configure the OTEL agent to export to Datadog too. Thank you!

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

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.

5mo

Replacing Grafana Elastic and Prometheus Setup with SigNoz

Dipen is trying to replace the current setup with SigNoz. Both Nocnica and Srikanth provide possible solutions including using OpenTelemetry and target allocator respectively.

3mo

Troubleshooting SigNoz Dashboard Visibility Issue

Naman had an issue with SigNoz not displaying services even though they've enabled it and sent data successfully. Srikanth engaged in investigation and troubleshooting, but the issue remained unresolved.

4mo

Troubleshooting SigNoz Auto-Instrumentation Configuration

igor is having trouble configuring auto-instrumentation for Java applications using SigNoz, with traces not appearing in the SigNoz UI. Prashant advises to check logs of the otel sidecar, use service name for endpoint, verify supported libraries, and test with telemetrygen. However, the issue still persists.

8mo

SigNoz Instrumentation Error in GCP/GKE with Python and FastAPI

Andre faced an error while instrumenting their app service with SigNoz. Srikanth identified the incorrect config and suggested the correct endpoint, resolving the issue.

7mo