Skip to content

[cloud] Add Akamai Cloud (Linode) as cloud entity#2756

Merged
joaopgrassi merged 5 commits intoopen-telemetry:mainfrom
paulojmdias:feat/linode_entity
Nov 3, 2025
Merged

[cloud] Add Akamai Cloud (Linode) as cloud entity#2756
joaopgrassi merged 5 commits intoopen-telemetry:mainfrom
paulojmdias:feat/linode_entity

Conversation

@paulojmdias
Copy link
Copy Markdown
Member

@paulojmdias paulojmdias commented Sep 9, 2025 •
edited
Loading

Relates to: open-telemetry/opentelemetry-collector-contrib#42544

Changes

This PR introduces new cloud.provider and cloud.platform values for Akamai Cloud (akamai_cloud) and Akamai Cloud Compute (akamai_cloud_compute), previously known as Linode.
These additions align with the new Linode resource detection processor in the Collector and ensure consistent attribute naming across all resources.

Merge requirement checklist

  • CONTRIBUTING.md guidelines followed.
  • Change log entry added, according to the guidelines in When to add a changelog entry.
    • If your PR does not need a change log, start the PR title with [chore]
  • Links to the prototypes or existing instrumentations (when adding or changing conventions)

@paulojmdias
[cloud] Add Linode as cloud entity
0769a5a 
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
@paulojmdias paulojmdias requested review from a team as code owners September 9, 2025 18:41
@github-actions github-actions bot added enhancement New feature or request area:cloud labels Sep 9, 2025
@paulojmdias paulojmdias mentioned this pull request Sep 9, 2025
Merged
@matt-hensley
Copy link
Copy Markdown
Contributor

matt-hensley commented Sep 9, 2025

Forwarded this PR to friends at Linode/Akamai. They're going to have someone review and provide feedback/approval.

@paulojmdias
Copy link
Copy Markdown
Member Author

paulojmdias commented Sep 9, 2025

Thank you @matt-hensley

I'm not sure if this shouldn't be named now as Akamai Cloud, so their input will be amazing

@cmcgalliard
Copy link
Copy Markdown

cmcgalliard commented Sep 10, 2025

Hey there,
Thanks for adding us to the list as a cloud entity! We'd prefer that we be considered Akamai first, so a slug of akamai_cloud and referenced as Akamai Cloud (Linode)

@paulojmdias
chore: rename Linode to Akamai Cloud
5059b84 
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
@paulojmdias paulojmdias changed the title [cloud] Add Linode as cloud entity [cloud] Add Akamai Cloud (Linode) as cloud entity Sep 10, 2025
@paulojmdias
Copy link
Copy Markdown
Member Author

paulojmdias commented Sep 10, 2025

@cmcga1125 updated accordingly

cmcgalliard
cmcgalliard approved these changes Sep 10, 2025
View reviewed changes
Copy link
Copy Markdown

@cmcgalliard cmcgalliard left a comment

Choose a reason for hiding this comment

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

Here's my approval, powerless as it may be on this repo :)

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 26, 2025

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Sep 26, 2025
@paulojmdias
Copy link
Copy Markdown
Member Author

paulojmdias commented Sep 26, 2025

/label -stale never-stale

@github-actions github-actions bot removed the Stale label Sep 27, 2025
@github-actions
Copy link
Copy Markdown

github-actions bot commented Oct 12, 2025

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Oct 12, 2025
@paulojmdias
Copy link
Copy Markdown
Member Author

paulojmdias commented Oct 12, 2025

/label -stale

@github-actions github-actions bot removed the Stale label Oct 13, 2025
joaopgrassi
joaopgrassi requested changes Oct 13, 2025
View reviewed changes
@github-project-automation github-project-automation bot moved this from Untriaged to Blocked in Semantic Conventions Triage Oct 13, 2025
@paulojmdias
chore: update id and value
958bb43 
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
@joaopgrassi joaopgrassi moved this from Blocked to Needs More Approval in Semantic Conventions Triage Oct 14, 2025
@joaopgrassi
Copy link
Copy Markdown
Member

joaopgrassi commented Oct 14, 2025

@cmcga1125 just to clarify things: (apologies, I didn't get at first you are from Akamai) if you think Akamai as a "Cloud provider" should be named akamai_cloud because that's how the company wants to be called, then it is fine to go that route.

My initial review was based on the feeling @paulojmdias used akamai_cloud because of the existing values, which we want to get rid of. We want to use namespaces (.) so all the existing ones will be changing at some point. Underscores are used on multi-word things, so if the provider name is "Akamai Cloud" then it is correct to use akamai_cloud.

Let me know if it isn't clear.

@cmcgalliard
Copy link
Copy Markdown

cmcgalliard commented Oct 14, 2025

Yeah, my concern would be confusion between our different products that Akamai offers. I want to be specific; we're discussing Akamai Cloud. Although I'm unsure if we would use akamai_cdn or akamai_security in this context, clearly labeling it as akamai_cloud would be beneficial.

@joaopgrassi
Copy link
Copy Markdown
Member

joaopgrassi commented Oct 15, 2025

Yeah, my concern would be confusion between our different products that Akamai offers. I want to be specific; we're discussing Akamai Cloud. Although I'm unsure if we would use akamai_cdn or akamai_security in this context, clearly labeling it as akamai_cloud would be beneficial.

Then what do you all think on using akamai_cloud for the provider, and then akamai_cloud.compute for the platform?

@cmcgalliard
Copy link
Copy Markdown

cmcgalliard commented Oct 15, 2025

I'm good with that!

@paulojmdias
chore: update Akamai
8f90df5 
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
@paulojmdias
Copy link
Copy Markdown
Member Author

paulojmdias commented Oct 15, 2025

@joaopgrassi @cmcga1125 updated accordingly.

lmolkova
lmolkova approved these changes Oct 29, 2025
View reviewed changes
Copy link
Copy Markdown
Member

@lmolkova lmolkova left a comment

Choose a reason for hiding this comment

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

Could you please also review other cloud attributes (specifically cloud.resource_id, cloud.region) and document any specifics on how they should be populated for Akamai cloud?

@lmolkova lmolkova moved this from Needs More Approval to Ready to be Merged in Semantic Conventions Triage Oct 29, 2025
@github-actions
Copy link
Copy Markdown

github-actions bot commented Nov 3, 2025

This PR contains changes to area(s) that do not have an active SIG/project and will be auto-closed:

  • cloud

Such changes may be rejected or put on hold until a new SIG/project is established.

Please refer to the Semantic Convention Areas
document to see the current active SIGs and also to learn how to kick start a new one.

@github-actions github-actions bot closed this Nov 3, 2025
@joaopgrassi joaopgrassi reopened this Nov 3, 2025
@joaopgrassi joaopgrassi added this pull request to the merge queue Nov 3, 2025
Merged via the queue into open-telemetry:main with commit c98d88b Nov 3, 2025
34 of 35 checks passed
@paulojmdias paulojmdias deleted the feat/linode_entity branch November 5, 2025 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jsuereth jsuereth jsuereth approved these changes

@lmolkova lmolkova lmolkova approved these changes

@joaopgrassi joaopgrassi joaopgrassi approved these changes

+1 more reviewer

@cmcgalliard cmcgalliard cmcgalliard approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

area:cloud enhancement New feature or request triage:accepted:ready

Projects

Semantic Conventions Triage
Archived in project

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@paulojmdias @matt-hensley @cmcgalliard @joaopgrassi @jsuereth @lmolkova