-
### What did you do?
(The sample code and commit with details [is in another commit](https://github.com/andrewhowdencom/courses.pito/commit/41a9168136a0ee81e29ba8893ea1d8b9d6ebf08d), but I will summa…
-
### What did you do?
Hi all :wave:,
we used the below code in order to send OTLP metrics directly to Prometheus with the following feature flags being set `--enable-feature=otlp-write-receiver, --…
-
### Is your feature request related to a problem? Please describe.
[Nacos](https://nacos.io/en-us/index.html) is an easy-to-use dynamic service discovery, configuration and service management platf…
-
**What should instrumenters be doing?**
For example, I'm instrumenting an RPC library:
* I write metrics for how long the exchange takes, how large the request was, and how large the response wa…
-
Assistants API has a slightly different model:
- messages are published individually
- the history is not re-published
- they have a bunch of identifiers: assistant_id, thread_id, run_id
-
The PR "Add container semantic conventions resource" (#39) introduced the attributes `container.command`, `container.command_line` and `container.command_args`.
These attributes in the PR had a "n…
-
As part of https://github.com/open-telemetry/semantic-conventions/pull/312, @tigrannajaryan suggested that we should discuss how a Collector can refine an existing service.instance.id. This issue is t…
-
We currently have some connection-level metrics defined for databases: https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-metrics.md
At the same time, connectio…
-
-
**What are you trying to achieve?**
I am trying to remove the use of `process.runtime.*` attributes for browser resource. In the Client Instrumentation SIG we agreed on using only `browser.` namesp…