Span operations are a short code identifying the type of operation the span is measuring. Span operations are low cardinality attributes - they should be as general as possible while still being human readable and useful.

Operations are expected to follow OpenTelemetry's semantic conventions as much as possible.

Below is a table containing a list of span operations that are recommended to be used.

Operations are expected to generally take the form: CATEGORY.ACTION, where the categories and actions can have optional identifiers. For example, a redis database operation takes the form db.sql.query, where db is the category, sql is the category identifier, and query is the action. Another example is a mobile app rendering it's screen. It would have the operation ui.load.hot, where ui is the category, load is the action, and hot is the action identifier.

It's important to keep categories consistent between sdks and integrations as they are used by Sentry in the Operations Breakdown feature. For example, both db.init and db.query will be categorized as database operations. The default operations breakdown config can be seen here.

Having both a category and action is recommended. Operations should be lowercased.

List of Operations

Browser

JS Frameworks

Web Server

Web Frameworks

Database

Serverless (FAAS)

Mobile

Messages/Queues