Skip to content

Conversation

@DavSanchez
Copy link
Contributor

@DavSanchez DavSanchez commented Oct 2, 2025

What this PR does / why we need it

This PR renames* the agent type for the New Relic Distribution for the OTel Collector (NRDOT). Now it's called com.newrelic.opentelemetry.collector.

Special notes for your reviewer

(* For compatibility reasons, as there will be configurations and deployments using the old agent type metadata, we now maintain both the old agent type name and the new, being equal in all respects besides the name. Fleet Control team also supports both so there should be no problems with new configs supporting the newer agent type.)

Remaining places to rename:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

  • Provided a meaningful title following conventional commit style.
  • Included a detailed description for the Pull Request.
  • Documentation under docs is aligned with the change.
  • Follows guidelines for Pull Requests in CONTRIBUTING.md.
  • Follows log level guidelines.

alvarocabanas
alvarocabanas previously approved these changes Oct 2, 2025
Copy link
Contributor

@alvarocabanas alvarocabanas left a comment

Choose a reason for hiding this comment

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

LGTM

@DavSanchez DavSanchez force-pushed the chore/rename-opentelemetry-collector-agent-type branch from 5ceecbc to 1a549d7 Compare October 3, 2025 07:54
@DavSanchez DavSanchez force-pushed the chore/rename-opentelemetry-collector-agent-type branch from 1a549d7 to d5a09e4 Compare October 3, 2025 11:32
@sigilioso
Copy link
Contributor

Could you update the PR description and briefly why we keep both agent-types?

sigilioso
sigilioso previously approved these changes Oct 3, 2025
Copy link
Contributor

@sigilioso sigilioso left a comment

Choose a reason for hiding this comment

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

Thanks! 🚀

Maybe a comment in the old agent-type saying that it is kept for backwards compatibility reasons might be useful for future us.

backoff_strategy:
type: fixed
backoff_delay: ${nr-var:backoff_delay}
# See com.newrelic.infrastructure Agent type for description of fields.
Copy link
Contributor

Choose a reason for hiding this comment

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

I've just noticed this comment, copy&pasted for sure but it is a bit misleading, isn't it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well the com.newrelic.infrastructure has some descriptions for the fields in comments, so perhaps it makes sense to leave this?

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh, now I get it. Let's leave it for now but it is really strange: we define the description field in the com.newrelic.infrastructure Agent Type (those fields could be actually used!) and here we add a comment asking to check the other Agent Type 🙃

"agents": {
"nrdot":{
"agent_type" : "newrelic/com.newrelic.opentelemetry.collector:0.1.0",
"agent_type" : "newrelic/io.opentelemetry.collector:0.1.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

We can change it again after we release, right?

Copy link
Contributor Author

@DavSanchez DavSanchez Oct 3, 2025

Choose a reason for hiding this comment

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

Yup! But I'm not entirely sure why it's faling... can we review it?

Agent types `io.opentelemetry.collector` and `com.newrelic.opentelemetry.collector` should be the same except for the name
@DavSanchez
Copy link
Contributor Author

Could you update the PR description and briefly why we keep both agent-types?

Added! Thanks for the heads up.

@DavSanchez DavSanchez added the k8s-extended-e2e Trigger extended k8s e2e on a PR label Oct 3, 2025
@DavSanchez DavSanchez merged commit 329a219 into main Oct 3, 2025
46 of 48 checks passed
@DavSanchez DavSanchez deleted the chore/rename-opentelemetry-collector-agent-type branch October 3, 2025 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

k8s-extended-e2e Trigger extended k8s e2e on a PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants