# SpanNames enum · @imqueue/opentelemetry

Source: https://imqueue.org/api/opentelemetry/latest/opentelemetry.spannames/
Published: 2026-08-01
Author: @imqueue maintainers (https://github.com/imqueue)
Package: @imqueue/opentelemetry 4.0.0 — generated reference, not hand-written

The span names this package emits. There are only three, and they identify the KIND of operation, not which method ran — the specific method is carried by the `resource.name` attribute ([AttributeNames.RESOURCE\_NAME](https://imqueue.org/api/opentelemetry/latest/opentelemetry.attributenames/)).

**Signature:**

```typescript
export declare enum SpanNames 
```

## Enumeration Members


| Member | Value | Description |
| --- | --- | --- |
| IMQ\_REQUEST | `"imq.request"` | A client issuing an RPC and awaiting the reply — the CLIENT side. |
| IMQ\_RESPONSE | `"imq.response"` | A service handling an inbound RPC — the SERVER side. |
| METHOD\_CALL | `"method.call"` | A method wrapped with the `traced` decorator. |


## Remarks

That split is what makes the traces groupable: a backend can aggregate all `imq.request` spans as "outbound RPC" and still break them down by resource. It also means filtering a dashboard by span name alone will never isolate a single method.