-
Notifications
You must be signed in to change notification settings - Fork 11
Allow for overriding the default honeycomb host #171
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 for overriding the default honeycomb host #171
Conversation
Support for situations where the Honeycomb host needs a tweak, such as when using the Refinery: https://docs.honeycomb.io/manage-data-volume/refinery/ Adding support for an environment variable `HONEYCOMB_HOST_OVERRIDE` but still using the default 443 port, and still assuming that the host is behind SSL. Bump core-telemetry to v0.2.8.0
|
Cheers @istathar. Thanks for the review. Will do 👍🏼 |
And fix up haddock, which contained a typo
Done. Also caught that I had the thing misspelled in the haddock, so that kinda proves that it was indeed a cumbersome name 😄 |
appendOption | ||
( Variable | ||
"HONEYCOMB_HOST" | ||
"Override the default API endpoint for occasions where telemetry needs to be proxied through an intermediate service. Default: api.honeycomb.io" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fyi I'm going to change this style to "... service (the default is api.honeycomb.io)." in a future commit, but that can wait.
Support for situations where the Honeycomb host needs a tweak, such as when using
the Refinery:
https://docs.honeycomb.io/manage-data-volume/refinery/
Adding support for an environment variable
HONEYCOMB_HOST_OVERRIDE
butstill using the default 443 port, and still assuming that the host is
behind SSL.
Bump core-telemetry to v0.2.8.0