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

feat(hpsf): add ability to produce otlp exporter to honeycomb #9

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

codeboten
Copy link
Contributor

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

  • adding template for collector_config
  • added tests for both refinery and collector config

@codeboten codeboten force-pushed the codeboten/add-collector branch from 7936c4f to 85b0fdd Compare December 19, 2024 23:09
Base automatically changed from kent.templated_components to main January 2, 2025 16:46
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>
@codeboten codeboten force-pushed the codeboten/add-collector branch from 85b0fdd to d07843e Compare January 8, 2025 19:12
@codeboten codeboten marked this pull request as ready for review January 8, 2025 19:59
@codeboten codeboten requested a review from a team as a code owner January 8, 2025 19:59
Copy link
Contributor

@MikeGoldsmith MikeGoldsmith left a 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]
Copy link
Contributor

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?

Copy link
Contributor Author

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

Comment on lines +1 to +2
API_Key: ${HONEYCOMB_TRACES_APIKEY}
API_URL: https://api.honeycomb.io
Copy link
Contributor

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 :|

Suggested change
API_Key: ${HONEYCOMB_TRACES_APIKEY}
API_URL: https://api.honeycomb.io
ApiKey: ${HONEYCOMB_TRACES_APIKEY}
ApiUrl: https://api.honeycomb.io

@kentquirk
Copy link
Contributor

I think this is now obsolete and should be closed. Is that correct?

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.

3 participants