Currently, OTel defines semantic conventions for HTTP for spans and metrics and there are none for logs. However, it makes sense to not reinvent the wheel and stick to the naming which is already available even though it's meant for a different pillar.
What needs to be done:
- dimension names used for HTTP and HTTP client log autocollection should be aligned with dimension names used in span/metric semantic conventions
cc @noahfalk @xakep139 @geeknoid
Currently, OTel defines semantic conventions for HTTP for spans and metrics and there are none for logs. However, it makes sense to not reinvent the wheel and stick to the naming which is already available even though it's meant for a different pillar.
What needs to be done:
cc @noahfalk @xakep139 @geeknoid