Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to start exometer graphite reporter via app.config file #481

Merged
merged 7 commits into from
Aug 7, 2015

Conversation

ppikula
Copy link
Contributor

@ppikula ppikula commented Aug 6, 2015

No description provided.

@ppikula ppikula changed the title Allow to start exometer graphite reporter using via ejabberd.cfg file Allow to start exometer graphite reporter using via app.config file Aug 6, 2015
Pawel Pikula added 3 commits August 6, 2015 15:06
The idea here is to allow using all available exomoter options - we can do this
by specifing them in the app.config file. User can start as many reporterts as
it want and mim just iterates over active reporters and adds subscripions for
them
You can see an additional option not listed in the Exometer docs - `mongooseim_report_interval`.
That option sets metrics resolution - in other words: how often Exometer gathers and sends metrics
throught reporters. By default that is 60 seconds.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/throught/through/

erszcz added a commit that referenced this pull request Aug 7, 2015
Allow to start exometer graphite reporter using via app.config file
@erszcz erszcz merged commit 7d0d73b into master Aug 7, 2015
@erszcz
Copy link
Member

erszcz commented Aug 7, 2015

Great code, man!

@erszcz erszcz deleted the start-exometer-via-conf branch August 7, 2015 13:20
@ppikula ppikula changed the title Allow to start exometer graphite reporter using via app.config file Allow to start exometer graphite reporter via app.config file Oct 5, 2015
@michalwski michalwski mentioned this pull request Oct 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants