Currently the traces that are logged via this module don't have environment metadata which means I cannot filter traces by environment in Elastic APM. e.g. development/test/staging/production
This feature and why it's useful is explained perfectly in this opentelemetry doco
Describe the solution you'd likeJust like we can set otel_service_name as per nginx-otel doco
I'd like to be able to set the environment with a directive called otel_service_environment
Bonus if you include service.node.name and service.version too.
Adding the value using a resource processor within the otel-collector, which works, but isn't right IMO.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4