Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / open-telemetry/semantic-conventions issues and pull requests

#1409 - DataCenter Resource

Issue - State: open - Opened by hdost over 3 years ago - 7 comments

#1362 - Proposal - HTTP request count semantic convention

Issue - State: open - Opened by nerdondon almost 2 years ago - 11 comments
Labels: enhancement

#1362 - Proposal - HTTP request count semantic convention

Issue - State: open - Opened by nerdondon almost 2 years ago - 11 comments
Labels: enhancement

#1299 - add Azure resource log mapping to OpenTelemetry

Issue - State: open - Opened by loomis-relativity almost 2 years ago - 1 comment

#1299 - add Azure resource log mapping to OpenTelemetry

Issue - State: open - Opened by loomis-relativity almost 2 years ago - 1 comment

#1230 - Define a standard way to identify synthetics request

Issue - State: open - Opened by pmm-sumo over 3 years ago - 3 comments
Labels: enhancement, area:browser

#1229 - Semantic convention for name and version of the instrumented library

Issue - State: open - Opened by arminru about 3 years ago - 1 comment
Labels: enhancement, area:new, triage:needs-triage

#1228 - Semantic convention for location attributes

Issue - State: open - Opened by ssidhu-apm over 2 years ago - 1 comment
Labels: enhancement, area:new

#1227 - Add RabbitMQ `message.header` attributes to semantic conventions

Issue - State: open - Opened by samimusallam almost 2 years ago - 6 comments
Labels: enhancement, area:messaging

#1226 - Establishing HTTP connection spec

Issue - State: open - Opened by mateuszrzeszutek over 1 year ago - 5 comments
Labels: enhancement, area:new, area:http

#1225 - Add histogram bucket boundaries to metric semconv yaml files

Issue - State: open - Opened by trask over 1 year ago
Labels: enhancement, tooling

#1224 - FaaS: provide span structure recommendations for multiple layers of instrumentation

Issue - State: open - Opened by lmolkova over 1 year ago - 4 comments
Labels: enhancement, triage:needs-triage, area:faas

#1224 - FaaS: provide span structure recommendations for multiple layers of instrumentation

Issue - State: open - Opened by lmolkova over 1 year ago - 4 comments
Labels: enhancement, triage:needs-triage, area:faas

#1223 - Should the HTTP semantic conventions say anything about capturing exceptions?

Issue - State: open - Opened by trask over 1 year ago - 2 comments
Labels: enhancement, triage:needs-triage, area:http

#1223 - Should the HTTP semantic conventions say anything about capturing exceptions?

Issue - State: open - Opened by trask over 1 year ago - 2 comments
Labels: enhancement, triage:needs-triage, area:http

#1222 - New JVM runtime environment metrics

Issue - State: open - Opened by roberttoyonaga over 1 year ago
Labels: enhancement, triage:needs-triage, area:jvm

#1220 - Messaging: record queue vs topic behavior correctly

Issue - State: open - Opened by lmolkova over 1 year ago - 11 comments

#1220 - Messaging: record queue vs topic behavior correctly

Issue - State: open - Opened by lmolkova over 1 year ago - 11 comments

#1219 - Modelling HTTP client response body capture

Issue - State: open - Opened by pavolloffay almost 4 years ago - 3 comments
Labels: enhancement, area:http

#1190 - Semantic conventions for JWT tokens.

Issue - State: open - Opened by hsblhsn over 2 years ago - 4 comments

#1187 - Messaging: per-message tracing when sending batches

Issue - State: open - Opened by lmolkova about 2 years ago - 29 comments
Labels: messaging-stability-blocker, area:messaging

#1163 - Define guidelines for messaging about excessive amounts of recorded data

Issue - State: open - Opened by jtmalinowski about 3 years ago - 5 comments

#1162 - Messaging: how to trace settle operation

Issue - State: open - Opened by lmolkova over 1 year ago - 3 comments
Labels: area:messaging

#1162 - Messaging: how to trace settle operation

Issue - State: open - Opened by lmolkova over 1 year ago - 3 comments
Labels: area:messaging

#1123 - Change peer.service to service.origin.name and service.target.name?

Issue - State: open - Opened by trask over 1 year ago - 6 comments

#1114 - Semantic conventions for SIP protocol

Issue - State: open - Opened by sirzooro over 2 years ago - 3 comments
Labels: enhancement

#1113 - Adding aws.region span attribute to the spec

Issue - State: open - Opened by Ma-Ba over 2 years ago - 4 comments

#1086 - "brief"s and "note"s of groups should be (optionally?) included in Markdown output

Issue - State: open - Opened by Oberon00 almost 4 years ago
Labels: enhancement, good first issue

#1057 - Semantic convention for span link names

Issue - State: open - Opened by sirzooro almost 2 years ago - 16 comments
Labels: enhancement

#1056 - Consider `http.status_code_class` attribute

Issue - State: open - Opened by alanwest almost 2 years ago - 10 comments

#1055 - hw.host.power/energy versus hw.power/energy metrics

Issue - State: open - Opened by sebastien-rosset over 1 year ago - 1 comment

#1055 - hw.host.power/energy versus hw.power/energy metrics

Issue - State: open - Opened by sebastien-rosset over 1 year ago - 1 comment

#1054 - renaming changes from 1.17.0 to 1.18.0 are not listed

Issue - State: open - Opened by frzifus over 1 year ago - 7 comments

#1038 - Add system memory metrics emitted by the JVM

Issue - State: open - Opened by trask over 1 year ago - 1 comment

#1038 - Add system memory metrics emitted by the JVM

Issue - State: open - Opened by trask over 1 year ago - 1 comment

#1033 - Add Geo fields from Elastic Common Schema

Issue - State: open - Opened by AlexanderWert almost 2 years ago - 5 comments

#1012 - Analyze the overlap between OpenTelemetry tracing attributes and ECS attributes

Issue - State: closed - Opened by trask over 1 year ago - 17 comments

#899 - http.route for client & server both as opposed to only server?

Issue - State: closed - Opened by dpk83 over 1 year ago - 14 comments

#899 - http.route for client & server both as opposed to only server?

Issue - State: closed - Opened by dpk83 over 1 year ago - 14 comments

#897 - Should metrics description be a full sentence?

Issue - State: open - Opened by reyang almost 2 years ago - 4 comments

#897 - Should metrics description be a full sentence?

Issue - State: open - Opened by reyang almost 2 years ago - 4 comments

#877 - Guidelines for redacting sensitive information

Issue - State: open - Opened by lmolkova over 1 year ago - 1 comment

#877 - Guidelines for redacting sensitive information

Issue - State: open - Opened by lmolkova over 1 year ago - 1 comment

#857 - Capture request and response bodies

Issue - State: open - Opened by pavolloffay almost 4 years ago - 15 comments
Labels: area:http

#835 - Add sustainability metrics and attributes to semantic conventions for hardware metrics

Issue - State: closed - Opened by bertysentry over 1 year ago - 13 comments
Labels: enhancement

#750 - Messaging: which semantics auxiliary operations should follow

Issue - State: open - Opened by lmolkova over 1 year ago - 2 comments

#717 - DB sanitization uniform format

Issue - State: closed - Opened by avzis over 1 year ago - 8 comments

#717 - DB sanitization uniform format

Issue - State: closed - Opened by avzis over 1 year ago - 8 comments

#716 - Add attribute `db.values` to database semantic conventions

Issue - State: closed - Opened by haddasbronfman over 1 year ago - 10 comments

#715 - Add CosmosDb Otel Specification

Issue - State: open - Opened by sourabh1007 almost 2 years ago - 10 comments
Labels: enhancement

#714 - db.name should be broken down into individual layers

Issue - State: closed - Opened by damiangarbacz almost 2 years ago - 3 comments

#713 - Database semantic conventions may violate namespacing guidelines

Issue - State: open - Opened by tigrannajaryan almost 2 years ago - 12 comments
Labels: help wanted

#712 - DB Convention does not cover batch/multi/envelope operations

Issue - State: closed - Opened by ndimiduk almost 3 years ago - 10 comments

#710 - Dealing with batching

Issue - State: closed - Opened by anuraaga over 3 years ago - 2 comments

#709 - Semantic Conventions for MongoDB

Issue - State: closed - Opened by toumorokoshi almost 4 years ago - 4 comments

#708 - Add db.statement sanitization/masking examples

Issue - State: closed - Opened by mateuszrzeszutek almost 4 years ago - 4 comments

#707 - Define metric semantic conventions for database operations

Issue - State: closed - Opened by jgals almost 4 years ago - 2 comments

#706 - Add semantic conventions for Elasticsearch client instrumentation

Issue - State: closed - Opened by estolfo over 1 year ago - 5 comments
Labels: enhancement

#658 - RPC `message` namespace is too generic

Issue - State: closed - Opened by lmolkova over 1 year ago - 1 comment
Labels: messaging-stability-blocker

#658 - RPC `message` namespace is too generic

Issue - State: closed - Opened by lmolkova over 1 year ago - 1 comment
Labels: messaging-stability-blocker

#657 - Add semantic conventions for "Process" spans for messaging scenarios

Issue - State: closed - Opened by pyohannes over 1 year ago - 2 comments
Labels: messaging-stability-blocker

#657 - Add semantic conventions for "Process" spans for messaging scenarios

Issue - State: closed - Opened by pyohannes over 1 year ago - 2 comments
Labels: messaging-stability-blocker

#654 - Clarify possible incompatibilities with CloudEvents Distributed Tracing extension

Issue - State: closed - Opened by pyohannes almost 3 years ago - 4 comments
Labels: messaging-stability-blocker, area:messaging, area:cloudevents

#653 - Create prototypes to validate the proposed semantic conventions for messaging

Issue - State: open - Opened by pyohannes over 1 year ago - 5 comments
Labels: messaging-stability-blocker

#653 - Create prototypes to validate the proposed semantic conventions for messaging

Issue - State: open - Opened by pyohannes over 1 year ago - 5 comments
Labels: messaging-stability-blocker

#652 - Clarify relationship between messaging, faas, and RPC

Issue - State: closed - Opened by anuraaga about 4 years ago - 21 comments
Labels: question, messaging-stability-blocker, area:faas, area:messaging, area:rpc

#649 - The protocol attribute should be removed for `system.network.connections` metrics

Issue - State: closed - Opened by codeboten about 2 years ago - 4 comments
Labels: system-semconv-wg-ga-blocker

#648 - Add system uptime metric

Issue - State: open - Opened by andrzej-stencel about 2 years ago - 13 comments
Labels: help wanted

#647 - Clarify semantics of system.cpu.time and system.cpu.utilization

Issue - State: closed - Opened by tigrannajaryan over 2 years ago - 8 comments
Labels: system-semconv-wg-ga-blocker

#531 - Proposal to add system.memory.slab

Issue - State: closed - Opened by rogercoll over 1 year ago - 4 comments
Labels: enhancement, system-semconv-wg-ga-blocker

#396 - Add agent resource type

Issue - State: open - Opened by jlegoff almost 2 years ago - 15 comments
Labels: enhancement

#396 - Add agent resource type

Issue - State: open - Opened by jlegoff almost 2 years ago - 15 comments
Labels: enhancement

#62 - network semconv change: local/remote side no longer attributable

Issue - State: open - Opened by Oberon00 over 1 year ago - 5 comments

#62 - network semconv change: local/remote side no longer attributable

Issue - State: open - Opened by Oberon00 over 1 year ago - 5 comments

#40 - Consider renaming process.runtime.jvm.* metrics to process.runtime.java.*

Issue - State: closed - Opened by jack-berg over 1 year ago - 4 comments

#40 - Consider renaming process.runtime.jvm.* metrics to process.runtime.java.*

Issue - State: closed - Opened by jack-berg over 1 year ago - 4 comments

#39 - Add container semantic conventions resource

Pull Request - State: closed - Opened by marcsanmi over 1 year ago - 1 comment

#38 - trace/http: Add semantic convention for total request and response length

Issue - State: closed - Opened by kamalmarhubi over 1 year ago - 2 comments
Labels: enhancement

#38 - trace/http: Add semantic convention for total request and response length

Issue - State: closed - Opened by kamalmarhubi over 1 year ago - 2 comments
Labels: enhancement

#37 - Publish a first release

Issue - State: closed - Opened by marcalff over 1 year ago - 4 comments

#37 - Publish a first release

Issue - State: closed - Opened by marcalff over 1 year ago - 4 comments

#36 - Update CHANGELOG with missing entry.

Pull Request - State: closed - Opened by carlosalberto over 1 year ago - 1 comment

#36 - Update CHANGELOG with missing entry.

Pull Request - State: closed - Opened by carlosalberto over 1 year ago - 1 comment

#35 - Limit HTTP request method cardinality: use one attribute (option C/E)

Pull Request - State: closed - Opened by lmolkova over 1 year ago - 9 comments

#35 - Limit HTTP request method cardinality: use one attribute (option C/E)

Pull Request - State: closed - Opened by lmolkova over 1 year ago - 9 comments

#34 - Limit HTTP request method cardinality: canonical method (Option B/D)

Pull Request - State: closed - Opened by lmolkova over 1 year ago - 5 comments

#34 - Limit HTTP request method cardinality: canonical method (Option B/D)

Pull Request - State: closed - Opened by lmolkova over 1 year ago - 5 comments

#33 - Transfer semconv issues from spec repo to this repo?

Issue - State: open - Opened by tigrannajaryan over 1 year ago - 2 comments

#33 - Transfer semconv issues from spec repo to this repo?

Issue - State: open - Opened by tigrannajaryan over 1 year ago - 2 comments

#32 - Capture kafka cluster.id

Issue - State: open - Opened by jack-berg over 2 years ago - 4 comments

#31 - Add a PR check to enforce Schema file presence/content if a semantic convention is changed

Issue - State: open - Opened by tigrannajaryan about 3 years ago - 4 comments
Labels: help wanted, tooling

#30 - Semantic conventions for browser events

Pull Request - State: closed - Opened by scheler over 1 year ago - 2 comments

#30 - Semantic conventions for browser events

Pull Request - State: closed - Opened by scheler over 1 year ago - 2 comments

#29 - Update team names following #25

Pull Request - State: closed - Opened by arminru over 1 year ago
Labels: editorial

#29 - Update team names following #25

Pull Request - State: closed - Opened by arminru over 1 year ago
Labels: editorial

#28 - Add tigrannajaryan as schema and logs codeowner

Pull Request - State: closed - Opened by tigrannajaryan over 1 year ago - 2 comments