The [HTTP spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-client) says these two attributes must be provided at span creation time - I think it makes sense to extend it over to all `net`-related instrumentations, cause these are supposed to be the logical peer name/port, which are supposed to be known before the connection is started/exchange is made. |
||
---|---|---|
.. | ||
elasticsearch-rest-5.0/javaagent | ||
elasticsearch-rest-6.4/javaagent | ||
elasticsearch-rest-7.0/javaagent | ||
elasticsearch-rest-common/javaagent | ||
elasticsearch-transport-5.0/javaagent | ||
elasticsearch-transport-5.3/javaagent | ||
elasticsearch-transport-6.0/javaagent | ||
elasticsearch-transport-common | ||
README.md |
README.md
Settings for the elasticsearch instrumentation
System property | Type | Default | Description |
---|---|---|---|
otel.instrumentation.elasticsearch.experimental-span-attributes |
`Boolean | false |
Enable the capture of experimental span attributes. |