12481fef89
add semantic conventions for heroku ( #3075 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-02-27 10:23:29 +01:00
1971550982
[editorial] Fix Tencent Cloud link ( #3231 )
2023-02-20 10:29:04 +01:00
e35ad2b9d5
[semantic_conventions/resource] fix google platform openshift naming ( #3095 )
2023-01-23 14:56:48 -08:00
656644592a
[resource] add openshift platform to all supported cloud providers ( #2985 )
2022-12-06 16:52:30 +01:00
b901d9dd76
add ibm cloud as a cloud provider ( #2965 )
2022-11-21 10:31:32 -08:00
3f7b7d02f9
Adopt attribute requirement levels in semantic conventions ( #2594 )
2022-06-14 08:02:55 -07:00
741ac62a15
Bump semantic conventions tool to v0.11.0 and refine enum wording ( #2399 )
2022-03-04 17:51:37 +01:00
540878944d
Add AWS App Runner as a cloud platform ( #2004 )
2021-10-15 15:59:50 +02:00
3e51df22d7
[semantic conventions] add tencent cloud as a cloud provider ( #2006 )
...
* feat: add tencent cloud as a cloud provider
* chore: tweaks
* chore: tweaks
* chore: lint
* chore: changelog
* chore: tweaks
* chore: tweaks
Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com>
2021-10-12 19:02:27 +00:00
227b4ff1b1
[semantic conventions] add alibaba cloud as a cloud provider ( #1831 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
2021-08-03 11:22:31 +00:00
ecec5145dc
Remove examples from enums. ( #1779 )
2021-06-29 12:54:59 -07:00
435182a274
Avoid using "infrastructure" terminology for all cloud ( #1530 )
...
* Avoid using "infrastructure" terminology for all cloud
Infrastructure in cloud has a specific connotation for concepts
explained in Infrastructure-as-a-Service (IaaS). Avoid this
termilogy because it's exclusive of some other services/platforms
that is represented by the "cloud" namespace.
Renaming "infrastructure_service" to "service" also due to the new
key length limits we are considering and infrastructure_service is
a lengthy choice.
2021-03-22 23:56:07 +01:00
580121698c
Rename cloud.zone to cloud.availability_zone ( #1495 )
...
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2021-03-11 11:02:16 +01:00
0e92f16571
Have consistent naming for Google Cloud services ( #1496 )
2021-03-04 17:48:22 +01:00
ece6eebf06
Clarify the cloud resource attributes ( #1481 )
2021-03-02 17:01:35 +01:00
eeff36dfd4
Add lifecycle statuses to all documents ( #1385 )
2021-02-04 15:06:46 +01:00
4f13d9c80b
regenerated tables after https://github.com/open-telemetry/build-tools/pull/24 ( #1342 )
2021-01-14 00:04:10 -08:00
27569327dc
added cloud.infrastructure_service attribute to resource spec ( #1112 )
...
Co-authored-by: Anuraag Agrawal <anuraaga@gmail.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2021-01-07 13:16:04 +01:00
b48cb0cff0
Fix typo in cloud resource convention. ( #1097 )
...
* Fix type in cloud convention.
* Run auto-md tool, cool!
2020-10-15 09:53:56 -07:00
31ec13ca2d
Add yaml for Cloud, Container, and Deployment resource attributes ( #1055 )
2020-10-09 16:02:07 +02:00
b971d97b32
Explicitly specify cloud.provider values for common cloud providers ( #1018 )
...
* Explicitly specify cloud.provider values for common cloud providers
Before some cloud provider values were given as an examples but it was still
left open to interpretation about what that meant. This makes it more explicit
that these are known values for those particular cloud providers.
* Apply suggestions from code review
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2020-09-29 14:12:05 +02:00
41869b89aa
Split resource semantic conventions in smaller files ( #727 )
...
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
2020-07-23 09:49:11 -04:00
Antoine Toulme