> ## Documentation Index
> Fetch the complete documentation index at: https://docs.honeycomb.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Attributes in the Honeycomb OpenTelemetry Android SDK

> Reference the standard attributes the Honeycomb OpenTelemetry Android SDK automatically adds to spans, covering environment, runtime, device, and SDK version data.

When you instrument your application using the Honeycomb OpenTelemetry Android SDK, spans automatically include a standard set of attributes.
These attributes provide essential context about the environment, runtime, device, and SDK versions--helping you understand where and how telemetry is being generated.

## Core Span Attributes

Every span includes these attributes:

* `device.manufacturer`: Device manufacturer, reported by [`android.os.Build.MANUFACTURER`](https://developer.android.com/reference/android/os/Build#MANUFACTURER).
* `device.model.identifier`: Model of the device, reported by [`android.os.Build.MODEL`](https://developer.android.com/reference/android/os/Build#MODEL).
* `device.model.name`: See `device.model.identifier`.
* `honeycomb.distro.runtime_version`: Operating system version on the device. See also `os.version`.
* `honeycomb.distro.version`: Version of the Honeycomb SDK in use.
* `os.description`: String describing the Android version, build ID, and SDK level.
* `os.name`: OS name. Always `android` for Android devices.
* `os.type`: OS type. Always `linux` on Linux platforms.
* `os.version`: Value of [`android.os.Build.VERSION.RELEASE`](https://developer.android.com/reference/android/os/Build.VERSION#RELEASE)
* `rum.sdk.version`: Version of the OpenTelemetry Android SDK in use.
* `screen.name`: Name of the current Activity or Fragment.
* `service.name`: Name of your application. Set via `setServiceName()`. Defaults to `unknown_service`.
* `service.version`: Version of your application. Set via `setServiceVersion()`.
* `telemetry.sdk.language`: Coding language for the Honeycomb SDK in use. Always `android` for the Honeycomb OpenTelemetry Android SDK.
* `telemetry.sdk.name`: Name of the telemetry SDK used to generate telemetry data. Always `opentelemetry` for the Honeycomb OpenTelemetry Android SDK.
* `telemetry.sdk.version`: Version of the base OpenTelemetry SDK in use.

## Application Not Responding Attributes

If you include the [application not responding instrumentation](https://github.com/open-telemetry/opentelemetry-android/tree/main/instrumentation/anr), then a span is created when the application becomes unresponsive. The span is named `ANR` and has this attribute:

* `exception.stacktrace`: (String) A representation of the call stack of the main thread at the time of the application not responding.

## Crash Attributes

If you include [crash instrumentation](https://github.com/open-telemetry/opentelemetry-android/tree/main/instrumentation/crash), a trace is emitted when an uncaught exception will terminate the application. The trace will be named `UncaughtException` and have these attributes:

* `exception.name`: (String) Name of the exception that triggered the crash.
* `exception.message`: (String) The exception message.
* `exception.stacktrace`: (String) A representation of the call stack of the main thread at the time of the application crash.
* `exception.escaped`: (Boolean) Indicates that the exception is escaping the scope of the span.
* `thread.name`: (String) The current thread name.
* `thread.id`: (Int) The current thread ID.

## Slow Rendering Attributes

If you include [slow rendering instrumentation](https://github.com/open-telemetry/opentelemetry-android/tree/main/instrumentation/slowrendering), then a trace is emitted for slow or frozen renders. Slow renders are renders greater than 16ms and frozen renders are greater than 700ms. The traces will be named either `slowRenders` or `frozenRenders` and have this attribute:

* `activity.name`: (String) Fully-qualified name of the Activity. For example: `"my.application.example/MainActivity"`

## Navigation Attributes

If you include [activity instrumentation](https://github.com/open-telemetry/opentelemetry-android/tree/main/instrumentation/activity) or [fragment instrumentation](https://github.com/open-telemetry/opentelemetry-android/tree/main/instrumentation/fragment), then navigation between Activities and Fragments is tracked through the `screen.name` attribute added to spans.

* `screen.name`: (String) Name of the current Activity or Fragment the user is viewing.