Semantic conventions for HBase client operations

Status: Development

• Spans
• Metrics

The Semantic Conventions for HBase extend and override the Database Semantic Conventions.

Spans

Status:

Spans representing calls to an HBase database adhere to the general Semantic Conventions for Database Client Spans.

db.system.name MUST be set to "hbase" and SHOULD be provided at span creation time.

Span name SHOULD follow the general database span name convention

Span kind SHOULD be CLIENT.

Span status SHOULD follow the Recording Errors document.

Attributes:

Key	Stability	Requirement Level	Value Type	Description	Example Values
db.operation.name		Required	string	The name of the operation or command being executed. [1]	findAndModify; HMSET; SELECT
db.collection.name		Conditionally Required If applicable.	string	The HBase table name. [2]	mytable; ns:table
db.namespace		Conditionally Required If applicable.	string	The HBase namespace. [3]	mynamespace
db.response.status_code		Conditionally Required If response was received.	string	Protocol-specific response code recorded as a string. [4]	200; 409; 14
error.type		Conditionally Required If and only if the operation failed.	string	Describes a class of error the operation ended with. [5]	timeout; java.net.UnknownHostException; server_certificate_invalid; 500
server.port		Conditionally Required [6]	int	Server port number. [7]	80; 8080; 443
db.operation.batch.size		Recommended	int	The number of database operations included in a batch operation. [8]	2; 3; 4
server.address		Recommended	string	Name of the database host. [9]	example.com; 10.1.2.80; /tmp/my.sock

[1] db.operation.name: It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.

For batch operations, if the individual operations are known to have the same operation name then that operation name SHOULD be used prepended by BATCH , otherwise db.operation.name SHOULD be BATCH.

[2] db.collection.name: It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization. If table name includes the namespace, the db.collection.name SHOULD be set to the full table name.

[3] db.namespace: If a database system has multiple namespace components, they SHOULD be concatenated from the most general to the most specific namespace component, using | as a separator between the components. Any missing components (and their associated separators) SHOULD be omitted. Semantic conventions for individual database systems SHOULD document what db.namespace means in the context of that system. It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.

[4] db.response.status_code: The status code returned by the database. Usually it represents an error code, but may also represent partial success, warning, or differentiate between various types of successful outcomes. Semantic conventions for individual database systems SHOULD document what db.response.status_code means in the context of that system.

[5] error.type: The error.type SHOULD match the db.response.status_code returned by the database or the client library, or the canonical name of exception that occurred. When using canonical exception type name, instrumentation SHOULD do the best effort to report the most relevant type. For example, if the original exception is wrapped into a generic one, the original exception SHOULD be preferred. Instrumentations SHOULD document how error.type is populated.

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

[7] server.port: 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.

[8] db.operation.batch.size: Except for empty batch requests described below, a batch operation contains two or more database operations explicitly submitted as separate operations in a single client call, protocol message, or database command.

Requests to batch APIs that contain only one operation SHOULD be modeled as single operations, not as batch operations.

A database call is not a batch operation solely because one operation accepts multiple operands, such as keys, rows, documents, points, or other data elements, including Redis MGET with multiple keys.

In batch APIs that execute the same parameterized operation with parameter sets, each parameter set represents one database operation for determining whether the request is a batch operation. Requests with only one parameter set SHOULD be modeled as single operations, not as batch operations.

db.operation.batch.size SHOULD be set to the number of operations in the batch. It SHOULD NOT be set for non-batch operations.

A request to execute a batch operation with no operations SHOULD also be treated as a batch operation, and db.operation.batch.size SHOULD be set to 0.

[9] server.address: 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.

The following attributes can be important for making sampling decisions and SHOULD be provided at span creation time (if provided at all):

• db.collection.name
• db.namespace
• db.operation.name
• server.address
• server.port

error.type 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.

Value	Description	Stability
_OTHER	A fallback error value to be used when the instrumentation doesn’t define a custom value.

Metrics

HBase client instrumentations SHOULD collect metrics according to the general Semantic Conventions for Database Client Metrics.

db.system.name MUST be set to "hbase".