127 lines
3.9 KiB
YAML
127 lines
3.9 KiB
YAML
name: Propose new semantic conventions
|
|
description: Propose new conventions you'd like to see in the OpenTelemetry project
|
|
labels: ["enhancement", "experts needed"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for your interest in contributing to the OpenTelemetry Semantic Conventions!
|
|
|
|
Substantial changes to the conventions follow [OTel project management]
|
|
(https://github.com/open-telemetry/community/blob/main/project-management.md) process
|
|
and usually require a group of people who are familiar with the domain,
|
|
are involved with instrumentation efforts, and are committed to be the point of contact for
|
|
pull requests, issues, and questions in this area.
|
|
|
|
Creating a new issue here is a great first step to find others interested in collaborating.
|
|
- type: dropdown
|
|
id: area
|
|
attributes:
|
|
label: Area(s)
|
|
description: Which area(s) does your new conventions concern? If none fits, please select `area:new`
|
|
multiple: true
|
|
options:
|
|
- area:new
|
|
# NOTE: The list below is autogenerated using `make generate-gh-issue-templates`
|
|
# DO NOT manually edit it.
|
|
# Start semconv area list
|
|
- area:android
|
|
- area:app
|
|
- area:artifact
|
|
- area:aspnetcore
|
|
- area:aws
|
|
- area:azure
|
|
- area:browser
|
|
- area:cassandra
|
|
- area:cicd
|
|
- area:client
|
|
- area:cloud
|
|
- area:cloudevents
|
|
- area:cloudfoundry
|
|
- area:code
|
|
- area:container
|
|
- area:cpu
|
|
- area:cpython
|
|
- area:db
|
|
- area:deployment
|
|
- area:destination
|
|
- area:device
|
|
- area:disk
|
|
- area:dns
|
|
- area:dotnet
|
|
- area:elasticsearch
|
|
- area:enduser
|
|
- area:error
|
|
- area:event
|
|
- area:exception
|
|
- area:faas
|
|
- area:feature-flag
|
|
- area:file
|
|
- area:gcp
|
|
- area:gen-ai
|
|
- area:geo
|
|
- area:go
|
|
- area:graphql
|
|
- area:hardware
|
|
- area:heroku
|
|
- area:host
|
|
- area:http
|
|
- area:ios
|
|
- area:jvm
|
|
- area:k8s
|
|
- area:linux
|
|
- area:log
|
|
- area:mainframe
|
|
- area:messaging
|
|
- area:network
|
|
- area:nfs
|
|
- area:nodejs
|
|
- area:oci
|
|
- area:onc-rpc
|
|
- area:openai
|
|
- area:opentracing
|
|
- area:os
|
|
- area:otel
|
|
- area:peer
|
|
- area:pprof
|
|
- area:process
|
|
- area:profile
|
|
- area:rpc
|
|
- area:security-rule
|
|
- area:server
|
|
- area:service
|
|
- area:session
|
|
- area:signalr
|
|
- area:source
|
|
- area:system
|
|
- area:telemetry
|
|
- area:test
|
|
- area:thread
|
|
- area:tls
|
|
- area:url
|
|
- area:user
|
|
- area:user-agent
|
|
- area:v8js
|
|
- area:vcs
|
|
- area:webengine
|
|
- area:zos
|
|
# End semconv area list
|
|
- type: textarea
|
|
attributes:
|
|
label: Propose new conventions
|
|
description: |
|
|
Please provide a brief description of the conventions, including
|
|
telemetry signals you'd like to define.
|
|
|
|
Consider specifying which instrumentations or systems would implement these
|
|
conventions and the benefits they would bring to the ecosystem.
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
attributes:
|
|
label: Tip
|
|
description: This element is static, used to render a helpful sub-heading for end-users and community members to help prioritize issues. Please leave as is.
|
|
options:
|
|
- <sub>[React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
|
|
default: 0
|