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 riemann resmon to use hostname or FQDN for events #41

Merged
merged 2 commits into from
May 22, 2013
Merged

Allow riemann resmon to use hostname or FQDN for events #41

merged 2 commits into from
May 22, 2013

Conversation

gsandie
Copy link
Contributor

@gsandie gsandie commented May 12, 2013

By default riemann-resmon was using the FQDN of the server it was
checking as the event hostname. This was slightly annoying as it meant
that went submitting metrics from an application you had to submit as
the FQDN.

This change allows you to select the behaviour, by default it will use
the hostname of the server it is checking.

Gavin Sandie added 2 commits May 1, 2013 18:36
By default riemann-resmon was using the FQDN of the server it was
checking as the event hostname. This was slightly annoying as it meant
that went submitting metrics from an application you had to submit as
the FQDN.

This change allows you to select the behaviour, by default it will use
the hostname of the server it is checking.
@gsandie
Copy link
Contributor Author

gsandie commented May 22, 2013

@aphyr We've been using this in production with no problems. Wasn't sure if I should merge it in, or if you'd want to take a look over it (merging my own work I might miss something glaringly wrong!).

@aphyr
Copy link
Collaborator

aphyr commented May 22, 2013

Yeah, I tend to want riemann-tools to use the local system's hostname as well, since I deploy these scripts as a part of the standard build pointing to localhost. :) +1

aphyr added a commit that referenced this pull request May 22, 2013
Allow riemann resmon to use hostname or FQDN for events
@aphyr aphyr merged commit 4e473ff into riemann:master May 22, 2013
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