--
You received this message because you are subscribed to the Google Groups "Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks for the quick response
Unfortunately I would like to keep the data from all my other collectors so I will just wait till 0.15.0.
Matthew
Do not fully understand how/when (including synchronization to avoid losing metrics) in any (push or pull model) the metrics are reset after they are gathered by the server?
The push gateway implementation does not clear/reset anything after successful push to gateway and don't see where/how Prometheus server would clear/reset metrics on each client on successful pull... ?
Looked at Collector class, CollectoryRegistry and associated sub-classes.
CollectorRegistry.clear() actually works like "unregister(Collector)" ... just for all Collectors and hence afterward, Hystrix publishes no metrics.
This would imply having to unregister and re-register all (Hystrix) methods for every scrape/push cycle... which makes no sense (and the writers to the Collectors would lose metrics during this process in a highly concurrent environment).
Clearly something is missed here... please advise.
Thank you.
Regarding the clients (attempting to use the Hystrix-Prometheus Java client suite)...
Do not fully understand how/when (including synchronization to avoid losing metrics) in any (push or pull model) the metrics are reset after they are gathered by the server?
The push gateway implementation does not clear/reset anything after successful push to gateway and don't see where/how Prometheus server would clear/reset metrics on each client on successful pull... ?
Looked at Collector class, CollectoryRegistry and associated sub-classes.
CollectorRegistry.clear() actually works like "unregister(Collector)" ... just for all Collectors and hence afterward, Hystrix publishes no metrics.
This would imply having to unregister and re-register all (Hystrix) methods for every scrape/push cycle... which makes no sense (and the writers to the Collectors would lose metrics during this process in a highly concurrent environment).
Clearly something is missed here... please advise.
Thank you.
On Thursday, June 4, 2015 at 11:46:33 PM UTC-4, mle...@gmail.com wrote:
> Hi there
>
> I have been experimenting with the graphite exporter and getting apache spark to send its metrics there. My first attempts didn't use a mapping file so all the metric names were exported 'as is' from the graphite format. Spark sends metrics from each executor (node) and includes the job name in the name of the metric so now it has hundreds of metric names in the drop down list and in the auto complete of the graph ui and prom dash. How can I delete them?
>
> To be clear I don't care about the data, it was just during testing.
>
> Thanks
> Matthew
--
You received this message because you are subscribed to the Google Groups "Prometheus Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-developers+unsub...@googlegroups.com.
To post to this group, send email to prometheus-developers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-developers/7dfaa06f-ccce-466e-a157-6848433a3daa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.