Skip to content

internal/telemetry: uniformize language name with other ways it's reported #1692

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

Merged

Conversation

paullegranddc
Copy link
Contributor

What does this PR do?

rename the language name from golang to go in the instrumentation telemetry client.

Motivation

The documentation for instrumentation-telemetry specified the value golang as the reported language name but this is not uniform with the existing ways it's reported. Since this feature is not GAed in dd-trace-go, let's fix it before we have to care about backward compatibility.

Describe how to test/QA your changes

Reviewer's Checklist

  • If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
  • Changed code has unit tests for its functionality.
  • If this interacts with the agent in a new way, a system test has been added.

Sorry, something went wrong.

@paullegranddc paullegranddc requested a review from a team as a code owner January 25, 2023 17:44
@paullegranddc paullegranddc changed the title internal/telemetry: unifromize language name with other ways it's reported internal/telemetry: uniformize language name with other ways it's reported Jan 25, 2023
Copy link
Contributor

@nsrip-dd nsrip-dd left a comment

Choose a reason for hiding this comment

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

Thanks Paul!

@nsrip-dd nsrip-dd added this to the Triage milestone Jan 25, 2023
@nsrip-dd nsrip-dd merged commit 4ab43e7 into main Jan 25, 2023
@nsrip-dd nsrip-dd deleted the paullgdc/instrumentation_teleemtry/standardize_language_name branch January 25, 2023 18:29
@ajgajg1134 ajgajg1134 modified the milestones: Triage, v1.47.0, v1.48.0 Jan 25, 2023
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.

None yet

3 participants