This message was deleted.

what emitter are you using & do you notice what kinds of metrics are being emitted?

Druid is emitting these metrics... can you please clarify do we need all these metrics and if not how it get rid of these metrics

druid_emitted_metrics_histogram_sum
druid_emitted_metrics_histogram_count
druid_emitted_metrics_histogram_bucket
druid_emitted_metrics

which emitter are you using though?

In the config of the service you are running check what

druid.emitter

is set as

ah yeah. that one doesn't have an ability to filter: i believe the thought is that the http server receiving the metrics would filter if necessary in your scenario, what's the http server? is it possible to configure filtering there?

@Gian Merlino Can you please ping me any docs that how can we perform the filtering on http emitter

if you're using grafana, maybe graphite? that one supports filtering You could also do filtering on the metric collector: whatever is listening to the HTTP emitter, you could set it up to discard certain metrics

@Gian Merlino I was using the druid-exporter running as pod which listen to one endpoint on which druid infra is emitting metrics. From druid exporter our prometheus is scraping metrics and we are visualising the dashboards in grafana. We can able to see the data in prometheus for some time and then the prometheus dosent scrape the metrics

did you try https://github.com/opstree/druid-exporter/blob/master/README.md the

--no-histogram

option ?

@Karan Kumar Sorry for late response. I had set the --no-histogram option now and the metrics emit size was in MB's now.But still it seems the value is high. can you tell what this option is for --metrics-cleanup-ttl

I think you should look at druid compaction : https://druid.apache.org/docs/latest/ingestion/compaction.html

To many segments also causes more emission of metrics right @Karan Kumar ?

I am not sure about metrics emission but its generally not a good place to be

Okay Thanks @Karan Kumar