Title | Link | # of reactions | Reactions |
---|---|---|---|
Capture request and response bodies | open-telemetry/semantic-conventions#857 | 29 | {'+1': 28, '-1': 1, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Introduce semantic conventions for modern AI (LLMs, vector databases, etc.) | open-telemetry/semantic-conventions#327 | 11 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 8, 'confused': 0, 'heart': 3, 'rocket': 0, 'eyes': 0} |
Improve GraphQL semantic conventions | open-telemetry/semantic-conventions#182 | 8 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 6, 'eyes': 1} |
Discuss ECS' field reuse concept for OTel semantic attributes | open-telemetry/semantic-conventions#339 | 7 | {'+1': 7, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Define semantic conventions for k8s metrics | open-telemetry/semantic-conventions#1032 | 6 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 6, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Http client and server span default collection behavior for url.full and url.query attributes |
open-telemetry/semantic-conventions#860 | 6 | {'+1': 3, '-1': 3, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Should metrics description be a full sentence? | open-telemetry/semantic-conventions#897 | 6 | {'+1': 6, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
[http] Publish migration plan for HTTP semconv changes. | open-telemetry/semantic-conventions#534 | 6 | {'+1': 6, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Adjust process.command_args and process.command_line to be opt-in |
open-telemetry/semantic-conventions#626 | 5 | {'+1': 5, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Processed/exported SDK metrics | open-telemetry/semantic-conventions#83 | 5 | {'+1': 5, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Proposal: Define mapping from k8s well-known labels to semconv | open-telemetry/semantic-conventions#236 | 5 | {'+1': 5, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Proposal: Decoupling Attribute definition from Attribute usage in models | open-telemetry/semantic-conventions#197 | 5 | {'+1': 5, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
[Proposal] Fork semantic-convention specific build-tools into a semantic-conventions-tools repository |
open-telemetry/semantic-conventions#767 | 5 | {'+1': 5, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
[logs] Add semantic conventions for durable identifiers | open-telemetry/semantic-conventions#372 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Attribute names: unicode on OTLP, only [a-z0-9._] in OTel semcov |
open-telemetry/semantic-conventions#1124 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add histogram bucket boundaries to metric semconv yaml files | open-telemetry/semantic-conventions#1225 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Adding aws.region span attribute to the spec | open-telemetry/semantic-conventions#1113 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Make requirement_level required | open-telemetry/semantic-conventions#892 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Create client side approver team | open-telemetry/semantic-conventions#856 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Proposal: include all removed/renamed/deprecated attribute keys in yaml | open-telemetry/semantic-conventions#214 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Document common metric names and when they should be used | open-telemetry/semantic-conventions#211 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Rename http.server.active_requests to http.server.current_requests? | open-telemetry/semantic-conventions#202 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Create semantic conventions for API Gateway | open-telemetry/semantic-conventions#183 | 4 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 2, 'eyes': 0} |
Markdown link check runs on entire repo | open-telemetry/semantic-conventions#332 | 4 | {'+1': 4, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Explain the source of registry files | open-telemetry/semantic-conventions#1204 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Introduction of a Synthetic Attribute for Server Span Telemetry | open-telemetry/semantic-conventions#1127 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Guidance on product/project name inside attribute/metric name | open-telemetry/semantic-conventions#608 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add anchors to individual attributes in a markdown table | open-telemetry/semantic-conventions#1041 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add kernel related semantic conventions | open-telemetry/semantic-conventions#66 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
What would be a good attribute for the name of a tenant? | open-telemetry/semantic-conventions#162 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Update Contributing.MD to describe how to use attribute registry when defining new semconv. | open-telemetry/semantic-conventions#532 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Transfer semconv issues from spec repo to this repo? | open-telemetry/semantic-conventions#33 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add Support for CloudFoundry | open-telemetry/semantic-conventions#622 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Convention for cancelled spans | open-telemetry/semantic-conventions#560 | 3 | {'+1': 3, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Common socket connection conventions | open-telemetry/semantic-conventions#454 | 3 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 2, 'rocket': 0, 'eyes': 0} |
User.id for authenticated user id | open-telemetry/semantic-conventions#1104 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Emitting log template + parameters? | open-telemetry/semantic-conventions#1283 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Should library-specific attributes be added to semantic conventions? | open-telemetry/semantic-conventions#1218 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Move attributes definitions to registry | open-telemetry/semantic-conventions#407 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Semantic convention for name and version of the instrumented library | open-telemetry/semantic-conventions#1229 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Markdown generation: render string examples with quotes | open-telemetry/semantic-conventions#1157 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Code generation: how to avoid naming collisions | open-telemetry/semantic-conventions#1118 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Semantic convention for location attributes | open-telemetry/semantic-conventions#1228 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
New JVM runtime environment metrics | open-telemetry/semantic-conventions#1222 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
CDN conventions | open-telemetry/semantic-conventions#958 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Do we need to distinguish client side and server side llm call? | open-telemetry/semantic-conventions#1079 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Event yaml definition should allow to document SeverityNumber | open-telemetry/semantic-conventions#828 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Messaging: per-message tracing when sending batches | open-telemetry/semantic-conventions#1187 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
[editorial] Rename pages under /docs/general/ to avoid general in the page name, etc |
open-telemetry/semantic-conventions#194 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Be more specific about span kinds for messaging operations | open-telemetry/semantic-conventions#1112 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add system uptime metric | open-telemetry/semantic-conventions#648 | 2 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 2, 'rocket': 0, 'eyes': 0} |
Potentially unbounded dimensions in Hardware metrics? | open-telemetry/semantic-conventions#63 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Database: write migration guide for (to-be) stable semconv | open-telemetry/semantic-conventions#1022 | 2 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 2, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
How to evolve stable conventions | open-telemetry/semantic-conventions#1017 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Track specification-related changes required for stabilizing messaging semantic conventions | open-telemetry/semantic-conventions#659 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Evaluate requirement level of db.statement | open-telemetry/semantic-conventions#754 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
General error.type definition should clarify that fully qualified exception type name should be used |
open-telemetry/semantic-conventions#855 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Clarification on metric semantic convention instrument naming | open-telemetry/semantic-conventions#816 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
General Attributes markdown is out of date and lists stable attributes as experimental | open-telemetry/semantic-conventions#762 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Consider adopting more log fields from ECS | open-telemetry/semantic-conventions#134 | 2 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 2, 'rocket': 0, 'eyes': 0} |
Document general attribute normalization conventions | open-telemetry/semantic-conventions#117 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
ECS User and Asset RFC | open-telemetry/semantic-conventions#116 | 2 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 2, 'rocket': 0, 'eyes': 0} |
Move JVM system metrics out of process.runtime.jvm.* | open-telemetry/semantic-conventions#41 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add a PR check to enforce Schema file presence/content if a semantic convention is changed | open-telemetry/semantic-conventions#31 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Consistent type to express date & time | open-telemetry/semantic-conventions#660 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Proposal: DB Attributes - rows count | open-telemetry/semantic-conventions#440 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Use seconds as default duration for RPC metrics | open-telemetry/semantic-conventions#383 | 2 | {'+1': 2, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
[editorial] Anchor IDs do not exist in v1.27 of docs | open-telemetry/semantic-conventions#1313 | 1 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 1, 'rocket': 0, 'eyes': 0} |
Move hardware metrics to the registry | open-telemetry/semantic-conventions#1309 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Run otel.io checks and codegen in any language as a prereq to release | open-telemetry/semantic-conventions#1317 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
When someone should use user.name/user.id ? | open-telemetry/semantic-conventions#1172 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
[cloud provider] host.id semantics are too broad |
open-telemetry/semantic-conventions#739 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Define rules for Kubernetes name and uid resource attributes | open-telemetry/semantic-conventions#430 | 1 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 1} |
[Feature request] Standard conventions for icon and color of resources and/or spans | open-telemetry/semantic-conventions#1266 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Semantic Conventions for Messaging Spans | open-telemetry/semantic-conventions#1205 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
How can Collectors refine service.instance.id | open-telemetry/semantic-conventions#1261 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Do we need event/logs approver team? | open-telemetry/semantic-conventions#1177 | 1 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 1} |
Database: add db.query.text as opt-in on metrics |
open-telemetry/semantic-conventions#1159 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Clean up yamls after https://github.com/open-telemetry/build-tools/issues/192 | open-telemetry/semantic-conventions#1232 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Decide on which db.system values to mark stable as part of initial db semconv stability |
open-telemetry/semantic-conventions#965 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add k8s.pod.ip attribute |
open-telemetry/semantic-conventions#1160 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
gcp.gce: Add instance group name | open-telemetry/semantic-conventions#905 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Process semconv: define common attributes and revisit requirement levels | open-telemetry/semantic-conventions#864 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add a human-readable message as an attribute representing the event | open-telemetry/semantic-conventions#1076 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Support stability definitions from OTEP 232 | open-telemetry/semantic-conventions#1096 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add http.connection.protocol_error_code to connection duration metric |
open-telemetry/semantic-conventions#1135 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Support reserving the namespace without specifying any attributes | open-telemetry/semantic-conventions#1197 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Semconv schema: add a field to record a version attribute was added in | open-telemetry/semantic-conventions#1138 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Database: allow db.query.text as opt-in on span names |
open-telemetry/semantic-conventions#1158 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Tracking issue for events yaml | open-telemetry/semantic-conventions#1133 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Checklist for declaring stability for messaging semantic conventions | open-telemetry/semantic-conventions#646 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Semantic conventions for SIP protocol | open-telemetry/semantic-conventions#1114 | 1 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 1} |
"brief"s and "note"s of groups should be (optionally?) included in Markdown output | open-telemetry/semantic-conventions#1086 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add footnote/reference to list of enum values | open-telemetry/semantic-conventions#1085 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Reconsidering what semantic conventions code generation should produce | open-telemetry/semantic-conventions#551 | 1 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 1} |
Pick a set of LLM systems to support/prototype | open-telemetry/semantic-conventions#839 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Metrics semconv should include value type of instrument and requirement levels in yaml and md | open-telemetry/semantic-conventions#591 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Create CLR metrics semantic convention | open-telemetry/semantic-conventions#956 | 1 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 1, 'rocket': 0, 'eyes': 0} |
Add Geo fields from Elastic Common Schema | open-telemetry/semantic-conventions#1033 | 1 | {'+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 1, 'rocket': 0, 'eyes': 0} |
Add system metrics reporting total memory capacity or clarify how to recover existing ones | open-telemetry/semantic-conventions#127 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Allowance for using Stored Operation IDs for Semantic conventions for GraphQL Server | open-telemetry/semantic-conventions#1011 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Document HBase attributes | open-telemetry/semantic-conventions#742 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Mail-related instrumentation attribute key convention | open-telemetry/semantic-conventions#927 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Clarify "type" in Resource semantic conventions | open-telemetry/semantic-conventions#929 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
What is the implication of breaking changes to stable semantic conventions | open-telemetry/semantic-conventions#772 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Should `db | messaging | rpc.system` be an instrumentation scope attribute? | open-telemetry/semantic-conventions#803 |
Request to create semconv-llm-approvers | open-telemetry/semantic-conventions#699 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add error.type to http.client.connection.duration metric |
open-telemetry/semantic-conventions#809 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Proposal to add otel.collector.receiver.name attribute | open-telemetry/semantic-conventions#759 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
process.command_args , container.command_args should be template attributes |
open-telemetry/semantic-conventions#790 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
FaaS - Incoming span kind | open-telemetry/semantic-conventions#696 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add process.cpu.count metric to semantic conventions for OS process metrics. |
open-telemetry/semantic-conventions#651 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Move "hardcoded" notes from metric semconv md files to the notes field in YAML |
open-telemetry/semantic-conventions#71 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Should we have metrics registry at some point? | open-telemetry/semantic-conventions#592 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Add documentation on how to publish patch releases to CONTRIBUTING.md | open-telemetry/semantic-conventions#539 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Define instrument name suffix *.used in the naming guidelines |
open-telemetry/semantic-conventions#508 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Problematic processing of optional metric dimensions | open-telemetry/semantic-conventions#492 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Document/warn about cardinality issue with attributes where input "comes from the user" | open-telemetry/semantic-conventions#485 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Change device prefix to mobile for mobile events? |
open-telemetry/semantic-conventions#548 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Introduce common configuration option for sanitisation of db.statement . |
open-telemetry/semantic-conventions#705 | 1 | {'+1': 1, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0} |
Last active
August 7, 2024 20:46
-
-
Save lmolkova/50565fc77fb417a5932028793b6d8137 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import requests | |
import time | |
def retry_request(url): | |
max_retries = 3 | |
retry_delay = 60 | |
for r in range(max_retries): | |
try: | |
print(f"Fetching {url}, try {r}") | |
# add your token here | |
response = requests.get(url, headers={"Authorization": "Bearer YOUR_PERSONAL_TOKEN"}) | |
if response.status_code == 200: | |
return response | |
print(f"Request failed: {response.json()}") | |
except requests.exceptions.RequestException as e: | |
print(f"Request failed: {e}") | |
print("Retrying in 1 minute...") | |
time.sleep(retry_delay) | |
return None | |
def reactions_to_dict(reactions): | |
keys = ["+1", "-1", "laugh", "hooray", "confused", "heart", "rocket", "eyes"] | |
return {k:v for k,v in reactions.items() if k in keys} | |
repo = "semantic-conventions" | |
issues_list = [] | |
reactions_count = {} | |
issues = {} | |
reactions = {} | |
for page in range(1, 10): | |
url = f'https://api.github.com/repos/open-telemetry/{repo}/issues?state=open&sort=updated&direction=desc&per_page=100&page={page}' | |
response = retry_request(url) | |
if response is None: | |
break | |
i = response.json() | |
if len(i) == 0: | |
break | |
print(f"Received {len(i)} issues") | |
issues_list.extend(i) | |
for issue in issues_list: | |
if 'pull_request' in issue: | |
continue | |
issue_id = issue['number'] | |
reactions_raw = issue['reactions'] | |
count = reactions_raw['total_count'] | |
if count > 0: | |
reactions_count[issue_id] = count | |
reactions[issue_id] = reactions_to_dict(reactions_raw) | |
issues[issue_id] = issue | |
print("| Title | Link | # of reactions | Reactions |") | |
print("| ------ | ---- | -------------- | --------- |") | |
for issue_id, count in sorted(reactions_count.items(), key=lambda r: r[1], reverse=True): | |
issue = issues[issue_id] | |
print(f"| {issue['title']} | {issue['html_url']} | {count} | {reactions[issue_id] } |") |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment