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

support configuring misc http headers for Graphite requests #1221

Merged
merged 1 commit into from
Jul 30, 2015

Conversation

Dieterbe
Copy link
Contributor

No description provided.

@captncraig
Copy link
Contributor

Code looks good to me. What is you use case for this?

@Dieterbe
Copy link
Contributor Author

We use the litmus graphite-kairosdb storage plugin which uses an x-org-id header for authorization

@kylebrandt
Copy link
Member

Litmus is raintanks upcoming sass monitoring product (for context)
On Jul 30, 2015 19:04, "Dieter Plaetinck" notifications@github.com wrote:

We use the litmus graphite-kairosdb storage plugin which uses an x-org-id
header for authorization


Reply to this email directly or view it on GitHub
#1221 (comment).

captncraig added a commit that referenced this pull request Jul 30, 2015
support configuring misc http headers for Graphite requests
@captncraig captncraig merged commit 4e4bbc5 into bosun-monitor:master Jul 30, 2015
@@ -44,6 +44,7 @@ Every variable is optional, though you should enable at least 1 backend.
* The items page.
* The graph page's tag list.
* graphiteHost: an ip, hostname, ip:port, hostname:port or a URL, defaults to standard http/https ports, defaults to "/render" path. Any non-zero path (even "/" overrides path)
* graphiteHeader: a http header to be sent to graphite on each request in 'key:value' format. optional. can be specified multiple times.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think you must add an exception to the seen func to make this specifiable multiple times.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

you're right, fixed in #1234
thanks for still looking out matt ;)

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.

4 participants