Semantic Conventions for Elasticsearch

Status: Experimental

The Semantic Conventions for Elasticsearch extend and override the Database Semantic Conventions that describe common database operations attributes in addition to the Semantic Conventions described on this page.

db.system MUST be set to "elasticsearch".

Span Name

The span name SHOULD be of the format <endpoint id>.

The elasticsearch endpoint identifier is used instead of the url path in order to reduce the cardinality of the span name, as the path could contain dynamic values. The endpoint id is the name field in the elasticsearch schema. If the endpoint id is not available, the span name SHOULD be the http.request.method.


AttributeTypeDescriptionExamplesRequirement LevelStability
db.operationstringThe endpoint identifier for the request. [1]search; ml.close_job; cat.aliasesRequiredExperimental
http.request.methodstringHTTP request method. [2]GET; POST; HEADRequiredStable
url.fullstringAbsolute URL describing a network resource according to RFC3986 [3]https://localhost:9200/index/_search?
db.elasticsearch.path_parts.<key>stringA dynamic value in the url path. [4]db.elasticsearch.path_parts.index=test-index; db.elasticsearch.path_parts.doc_id=123Conditionally Required when the url has dynamic valuesExperimental
server.portintServer port number. [5]80; 8080; 443Conditionally Required [6]Stable
db.elasticsearch.cluster.namestringRepresents the identifier of an Elasticsearch cluster.e9106fc68e3044f0b1475b04bf4ffd5fRecommended [7]Experimental
db.instance.idstringAn identifier (address, unique name, or any other identifier) of the database instance that is executing queries or mutations on the current connection. This is useful in cases where the database is running in a clustered environment and the instrumentation is able to record the node executing the query. The client may obtain this value in databases like MySQL using queries like select @@hostname.mysql-e26b99z.example.comRecommended [8]Experimental
db.statementstringThe request body for a search-type query, as a json string."{\"query\":{\"term\":{\"\":\"kimchy\"}}}"Recommended [9]Experimental
network.peer.addressstringPeer address of the database node where the operation was performed. [10]; /tmp/my.sockRecommendedStable
network.peer.portintPeer port number of the network connection.65123Recommended if and only if network.peer.address is set.Stable
server.addressstringName of the database host. [11];; /tmp/my.sockRecommendedStable

[1]: When setting this to an SQL keyword, it is not recommended to attempt any client-side parsing of db.statement just to get this property, but it should be set if the operation name is provided by the library being instrumented. If the SQL statement has an ambiguous operation, or performs more than one operation, this value may be omitted.

[2]: HTTP request method value SHOULD be “known” to the instrumentation. By default, this convention defines “known” methods as the ones listed in RFC9110 and the PATCH method defined in RFC5789.

If the HTTP request method is not known to instrumentation, it MUST set the http.request.method attribute to _OTHER.

If the HTTP instrumentation could end up converting valid HTTP request methods to _OTHER, then it MUST provide a way to override the list of known HTTP methods. If this override is done via environment variable, then the environment variable MUST be named OTEL_INSTRUMENTATION_HTTP_KNOWN_METHODS and support a comma-separated list of case-sensitive known HTTP methods (this list MUST be a full override of the default known method, it is not a list of known methods in addition to the defaults).

HTTP method names are case-sensitive and http.request.method attribute value MUST match a known HTTP method name exactly. Instrumentations for specific web frameworks that consider HTTP methods to be case insensitive, SHOULD populate a canonical equivalent. Tracing instrumentations that do so, MUST also set http.request.method_original to the original value.

[3]: For network calls, URL usually has scheme://host[:port][path][?query][#fragment] format, where the fragment is not transmitted over HTTP, but if it is known, it SHOULD be included nevertheless. url.full MUST NOT contain credentials passed via URL in form of In such case username and password SHOULD be redacted and attribute’s value SHOULD be url.full SHOULD capture the absolute URL when it is available (or can be reconstructed). Sensitive content provided in url.full SHOULD be scrubbed when instrumentations can identify it.

[4]: Many Elasticsearch url paths allow dynamic values. These SHOULD be recorded in span attributes in the format db.elasticsearch.path_parts.<key>, where <key> is the url path part name. The implementation SHOULD reference the elasticsearch schema in order to map the path part values to their names.

[5]: When observed from the client side, and when communicating through an intermediary, server.port SHOULD represent the server port behind any intermediaries, for example proxies, if it’s available.

[6]: If using a port other than the default port for this DBMS and if server.address is set.

[7]: When communicating with an Elastic Cloud deployment, this should be collected from the “X-Found-Handling-Cluster” HTTP response header.

[8]: When communicating with an Elastic Cloud deployment, this should be collected from the “X-Found-Handling-Instance” HTTP response header.

[9]: Should be collected by default for search-type queries and only if there is sanitization that excludes sensitive information.

[10]: If a database operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.

[11]: When observed from the client side, and when communicating through an intermediary, server.address SHOULD represent the server address behind any intermediaries, for example proxies, if it’s available.

http.request.method has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

DELETEDELETE method.Stable
GETGET method.Stable
HEADHEAD method.Stable
PATCHPATCH method.Stable
POSTPOST method.Stable
PUTPUT method.Stable
TRACETRACE method.Stable
_OTHERAny HTTP method that the instrumentation has no prior knowledge of.Stable


Span name"search"