This message was deleted.

Hi Aman, which part are you trying to achieve? I'm using Istio and SigNoz

I have my application developed with opentelemetry and istio is running on the cluster. So istio should aggregate the data and send it to kiali and then signoz will use that data to visualise

@Prashant Shahi would you have more insights on this

@Aman Upadhyay You can enable Zipkin receiver in SigNoz OtelCollector, and send traces from Istio. • Include the following in OtelCollector config:

receivers:
  zipkin:
    endpoint: 0.0.0.0:9411
  ...

• Include

zipkin

in the

traces

pipeline.

pipelines:
    traces:
      receivers: [zipkin, ...]
      ...

• Configure SigNoz OtelCollector Zipkin address in Istio https://istio.io/latest/docs/ops/integrations/zipkin/#option-2-customizable-install

Hey @Prashant Shahi yesterday @Srikanth Chekuri and I found a memory leak on query service generated by istio metrics

Hi Lucas! Thanks for mentioning it on the thread.

not actually, 10k samples broke the whole thing

oh, I see.

It’s probably specific to their environment. I think I misquoted what we were doing.

@Pranay @Prashant Shahi @Lucas Carlos Thanks for responding to my query. Will follow the approach suggest by you guys .

Hey @Aman Upadhyay the scraping works fine, we just found that the dashboards must be edited, just remove

max(up *)

statement from the queries, this will try to load all

up

within your queries and potentially overload query-service

Cool

@Lucas Carlos Whenever you find time, would be great if you can share a note on how you monitor Istio with SigNoz. We can also publish in tutorials sections of our docs if that works for you. Would be helpful for other community members who are looking to monitor Istio 🙂

Yes, for sure

Awesome! If it's simpler - you can just open a PR here - https://github.com/SigNoz/signoz.io/tree/main/docs/tutorial