Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make otelarrow receiver metrics consistent #36334

Open
jmacd opened this issue Nov 12, 2024 · 2 comments · May be fixed by #36359
Open

Make otelarrow receiver metrics consistent #36334

jmacd opened this issue Nov 12, 2024 · 2 comments · May be fixed by #36359

Comments

@jmacd
Copy link
Contributor

jmacd commented Nov 12, 2024

Component(s)

exporter/otelarrow, receiver/otelarrow

Describe the issue you're reporting

The OTel-Arrow project's exporter and receiver are named "otelarrow". The spans and metrics they produce have "otel_arrow" as a substring, and this feels like a consistency problem worth resolving before the components can be marked stable.

Moreover, metrics which are applicable to both OTLP and OTel-Arrow code paths should be made consistent. Presently, the OTLP path does not instrument in-flight bytes, items, and requests.

Copy link
Contributor

Pinging code owners for receiver/otelarrow: @jmacd @moh-osman3. See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

Pinging code owners for exporter/otelarrow: @jmacd @moh-osman3 @lquerel. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@jmacd jmacd changed the title Use consistent "otelarrow", not "otel_arrow" in otelarrowreceiver, otelarrowexporter Make otelarrow receiver metrics consistent Nov 13, 2024
@jmacd jmacd linked a pull request Nov 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant