This message was deleted.
s
This message was deleted.
i
in general, you need couple of things: 1. otel collector to store the traces/metrics in the other datasource(there are a lot already, but check your source is already implemented, if not, need to implement it) 2. add new reader in query - service, it should implement all methods that are in reader interface, with the appropriate response in general, i use clickhouse, but i altered the code in order to improve performance(at least in my case, but i think it will fit all cases) can be altered even further, but i still did not have a time to check it on high scale, with server with 2vcpu and 8gb of ram, i can handle 100 million traces with ease(avg response under 500ms, clickhouse is on cloud, while my query service is locally, so there is some latency there)
a
Ok, I am pretty new to signoz, and I am confused a bit. Currently we have zipkin to store traces (cassandra db) and view distributed traces.. how does signoz come to picture? Can I use it as an alternate to zipkin? What does signoz use clickhouse to store? traces/metric? (My question was if I can use cassandra/postrges as a backend for signoz to store traces/metrics etc. ) Or can signoz query from another zipkin instance?
i
how does signoz come to picture? Can I use it as an alternate to zipkin? - yes, it is replacement for zipkin/jaeger or any apm tool What does signoz use clickhouse to store? traces/metric? - in general both, i currently only store traces, but currently there is work in progress to store metrics as well(from what i saw in github repo, maybe one of the mainteners can elaborate a bit more, there is also roadmap in the site if you want ot see) Or can signoz query from another zipkin instance? - no, as signoz stores the data bit differently, table schemas most likely not be the same, and needs to be adjust accordingly if you want to use different store in general, i’ve used cassnadra with apache skywalking, it is harder to maintain, and performance not come close to clickhouse(for the scale i used) give it a try with clickhouse see if it fits your needs if you are using agent which is different then opentelemtry protocol, then your code might need to be changed as well
🙌 1
a
@User perfect answers 💯. Thanks!
@User I am one of the maintainers of SigNoz. As Itzik mentioned, SigNoz is a complete replacement of any APM tool. Currently we ingest trace data only and generate metrics by crunching trace data. Also, our metrics ingestion is WIP and should be available next week. This would enable • Ingestion of any custom metrics generated from applications using otel/prometheus libraries • Infrastructure and cluster metrics • Metrics from any components like redis, kafka, nginx, etc
I found cassandra and postgres very limited in enabling telemetry data. Apart from performance, running aggregates on filtered trace data seemed very important to us which can be enabled only by columnar databases. As said, SigNoz should be more performant as compared to Jaeger/Zipkin both in terms of latency and storage.
We use opentelemetry collector to receive data. It has provision to receive data in opentelemetry format (OTLP) or zipkin or jaeger. So your existing instrumentation with Zipkin should not change. You need to run SigNoz and point your applications to send telemetry data to SigNoz rather than Zipkin agent endpoint. That should do.
You need to change a couple of lines in config to enable zipkin ingestion. Let me know if you are there and I shall help you with that
a
Thank you @User!. @User, Our organization is currently limited to support only postgres or cassandra as a service and that is the reason I was looking for a way to install signoz using one of them, But that doesn't seems possible. Our reason to adopted zipkin was because it could store everything in cassandra. I will check with internal teams to see if we can have clickhouse somehow. Thank you!
I do understand the benefits of ClickHouse 🙂
🙌 1
a
I will check with internal teams to see if we can have clickhouse somehow.
Sure thing. Let us know 🙂
175 Views