This message was deleted.
# troubleshootings
Slackbot
10/13/2022, 12:07 PMThis message was deleted.
r
Razvan Brinzea
10/13/2022, 12:09 PMthe context is: the current implementation of the Prometheus pushgateway strategy for peons is not very helpful to me, since metrics are only flushed when each task is finished. I think that this is greatly improved by https://github.com/apache/druid/pull/13034 , but this was not part of the latest release
Razvan Brinzea
10/13/2022, 12:10 PMso I'd like to keep using the http emitter strictly for real-time ingestion metrics, and use the prometheus emitter on the MiddleManager for other metrics (mainly interested in investigating query performance)
c
Cristian Popa
10/13/2022, 7:28 PMI think what you want may be this, not sure if it works but I'd think this way you can pass specific property to the peon:
druid.indexer.runner.javaOpts=-server -Xms512m -Xmx512m -Duser.timezone=UTC -Dfile.encoding=UTF-8 -XX:+ExitOnOutOfMemoryError -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager -Ddruid.emitter=http
Cristian Popa
10/13/2022, 7:28 PM-Ddruid.emitter=http is the key here
Cristian Popa
10/14/2022, 2:25 AMOr maybe even more elegant , use
druid.indexer.runner.javaOptsArrayCristian Popa
10/14/2022, 2:25 AMin MM runtime properties
Cristian Popa
10/14/2022, 2:26 AMdruid.indexer.runner.javaOptsArray=["druid.emitter=http"]r
Razvan Brinzea
10/17/2022, 12:49 PMThanks for the suggestions! Unfortunately this still didn't work for me - no matter what I do I can't seem to override the emitter for Peons. But I did find a workaround - I'll use a composing emitter with both HTTP and prometheus, so I'll get the best of both. I don't really mind the additional overhead at this point
2 Views