You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm curious why we choose to use Dropwizard's graphite reporter directly. Instead, we could publish all the metrics to MetricRegistry and configure the reporter (graphite, statsd, JMX etc) using the config file. I'm thinking of adding support it but wondering why it wasn't done at first place because of some problems or would cause problems. Suggestions/ thoughts?
The text was updated successfully, but these errors were encountered:
Hi, I'm curious why we choose to use Dropwizard's graphite reporter directly. Instead, we could publish all the metrics to MetricRegistry and configure the reporter (graphite, statsd, JMX etc) using the config file. I'm thinking of adding support it but wondering why it wasn't done at first place because of some problems or would cause problems. Suggestions/ thoughts?
The text was updated successfully, but these errors were encountered: