vipul-mykaarma opened a new issue, #16479:
URL: https://github.com/apache/druid/issues/16479

   Please provide a detailed title (e.g. "Broker crashes when using TopN query 
with Bound filter" instead of just "Broker crashes").
   
   ### Affected Version
   
   The Druid version where the problem was encountered : 29.0.1
   
   ### Description
   
   Task metrics  like task_run_time, are commented with # when the metrics page 
is looked up 
    This metric is only available if the TaskCountStatsMonitor module is 
included.
   
   Please include as much detailed information about the problem as possible.
   - Running it a single server config small
   - Configurations in use
   
   Common.runtime.properties: 
   
   druid.emitter=prometheus
   druid.emitter.prometheus.strategy=exporter
   druid.emitter.prometheus.port=8088
   druid.prometheus.emitter.monitored-processes=["broker", "historical", 
"realtime", "overlord", "middleManager", "coordinator"]
   druid.server.http.healthCheck=true
   
   Coordinator. runtime.properties 
   
   
druid.monitoring.monitors=["org.apache.druid.server.metrics.TaskCountStatsMonitor"]
   
   druid.emitter.prometheus.port=8089
   druid.emitter=prometheus
   druid.emitter.prometheus.strategy=exporter
   druid.emitter.prometheus.http.type=multi
   druid.emitter.prometheus.http.multi.feed=[metrics, task, ingest]
   
   
   on looking up <ip:8088>, <ip:8089>
   
   # HELP druid_task_failed_count_total Number of failed tasks per emission 
period. This metric is only available if the TaskCountStatsMonitor module is 
included.
   # TYPE druid_task_failed_count_total counter
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to