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

[exporter/mezmoexporter] Remove hardcoded "otel" hostname #13410

Merged
merged 3 commits into from
Aug 22, 2022

Conversation

jsumners
Copy link
Contributor

Description:
This change removes the hardcoded "otel" hostname that was embedded
in outgoing logs data. It is replaced by:

  1. Sending to a new collector endpoint that does not require the
    hostname parameter.
  2. Recognizing the "host.name" resource attribute and using that
    value to fill in log metadata recognized upstream.

This is a breaking change, and as such will generate a startup
error if the exporter is configured to send to an endpoint that
does not support this feature.

Testing:

The changes in this PR were used to send data to the Mezmo service. The collector was configured with both a syslog receiver and a tcplog receiver. Data from each receiver was correctly received and stored in the Mezmo system.

Documentation:

All documentation associated with this exporter was updated to match the new requirements and changes to Mezmo's upstream documentation (re: our name change from LogDNA to Mezmo).

@jsumners jsumners requested a review from a team August 18, 2022 12:16
@jsumners jsumners requested a review from dashpole as a code owner August 18, 2022 12:16
@jsumners jsumners marked this pull request as draft August 18, 2022 12:16
@jsumners jsumners force-pushed the mezmo/replace-hardcoded-host branch from e757267 to 9f14141 Compare August 18, 2022 12:22
@jsumners jsumners marked this pull request as ready for review August 18, 2022 12:22
@jsumners jsumners force-pushed the mezmo/replace-hardcoded-host branch from 587b861 to 278bf7f Compare August 18, 2022 14:24
This change removes the hardcoded "otel" hostname that was embedded
in outgoing logs data. It is replaced by:

1. Sending to a new collector endpoint that does not require the
hostname parameter.
2. Recognizing the "host.name" resource attribute and using that
value to fill in log metadata recognized upstream.

This is a breaking change, and as such will generate a startup
error if the exporter is configured to send to an endpoint that
does not support this feature.
@jsumners jsumners force-pushed the mezmo/replace-hardcoded-host branch from 278bf7f to 2723f8a Compare August 18, 2022 17:03
@jsumners
Copy link
Contributor Author

Is it necessary to keep updating the branch? Prior to the the changelog yaml files we needed to do so due to conflicts in the changelog file. Thankfully, that's no longer an issue. But GitHub still keeps complaining that the branch is out-of-date with the base branch every few hours (i.e. I'll updated, merges will happen, and I'll need to update it again).

@jsumners
Copy link
Contributor Author

Is there anything else I need to do to move this one forward?

@dashpole dashpole added the ready to merge Code review completed; ready to merge by maintainers label Aug 22, 2022
@bogdandrutu bogdandrutu merged commit 9f8b115 into open-telemetry:main Aug 22, 2022
@jsumners jsumners deleted the mezmo/replace-hardcoded-host branch August 22, 2022 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exporter/mezmo ready to merge Code review completed; ready to merge by maintainers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants