# AttributeNames enum · @imqueue/opentelemetry

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

Attribute keys this package sets on every span it creates.

**Signature:**

```typescript
export declare enum AttributeNames 
```

## Enumeration Members


| Member | Value | Description |
| --- | --- | --- |
| COMPONENT | `"component"` | Always `'imq'`, marking the span as produced by this instrumentation. |
| ERROR\_MESSAGE | `"error.message"` | Failure detail, set alongside an `ERROR` span status. |
| IMQ\_CLIENT | `"imq.client"` | Which client issued the request, taken from the IMQ request's `from`. |
| RESOURCE\_NAME | `"resource.name"` | What ran, as `Name.method` — the IMQ service and method for an RPC span, or `ClassName.methodName` for a `traced` method. This is the field to group by; the span name only says which of the three kinds it is. |
| SERVICE\_NAME | `"service.name"` | The IMQ service involved in the call, or the host package name. |
| SPAN\_KIND | `"span.kind"` | `'server'` or `'client'` — see [TraceKind](https://imqueue.org/api/opentelemetry/latest/opentelemetry.tracekind/). Duplicates the OpenTelemetry span kind as a plain attribute, for backends that only read attributes. |


## Remarks

These are the pre-OpenTelemetry Datadog-style keys (`resource.name`, `service.name`, `component`) rather than the current OpenTelemetry semantic conventions, which is what lets the spans land in a Datadog-shaped backend unmodified. If your backend expects semantic-convention names instead, remap them in a span processor — nothing here reads these keys back.