-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat(hpsf): add ability to produce otlp exporter to honeycomb #9
base: main
Are you sure you want to change the base?
Conversation
7936c4f
to
85b0fdd
Compare
This PR adds the ability to use the HoneycombExporter component template to produce collector configuration to emit otlphttp to honeycomb. It also adds the following: - ability to set slices of maps as values in templates - output tests for a HoneycombExporter Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
85b0fdd
to
d07843e
Compare
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.
Looks good. Left a non-blocking query and suggestion.
The compression to use when sending data to Honeycomb. | ||
This is normally gzip, but can be overridden. | ||
type: string | ||
validations: [nonblank] |
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.
Does having this as nonblank
mean you have to provide a value. Is none
okay?
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.
currently validations are not enforced. none
will be ok... i suspect nonblank
will just mean don't put an empty string here
API_Key: ${HONEYCOMB_TRACES_APIKEY} | ||
API_URL: https://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.
Naming is always fun. There's 3 different forms here; API_Key
, AcessKeys
and sendKey
:|
API_Key: ${HONEYCOMB_TRACES_APIKEY} | |
API_URL: https://api.honeycomb.io | |
ApiKey: ${HONEYCOMB_TRACES_APIKEY} | |
ApiUrl: https://api.honeycomb.io |
I think this is now obsolete and should be closed. Is that correct? |
Which problem is this PR solving?
This PR adds the ability to use the HoneycombExporter component template to produce collector configuration to emit otlphttp to honeycomb.
Short description of the changes