> ## 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.

# Resource Detection

<Badge className="hny-badge-enterprise-addon" stroke>Ent+</Badge>

<Note>
  This feature is available as an add-on for the [Honeycomb Enterprise plan](https://www.honeycomb.io/pricing/).
  Please contact your Honeycomb account team for details.
</Note>

## Description

The resource detection processor can be used to detect resource information from the host, in a\
format that conforms to the [OpenTelemetry resource semantic conventions](https://opentelemetry.io/docs/concepts/semantic-conventions/), and append or override the resource value in telemetry data with this information.

## Supported Types

| Metrics | Logs | Traces | Bindplane Collector |
| ------- | ---- | ------ | ------------------- |
| ✓       | ✓    | ✓      | `v1.40.0`+          |

## Configuration Table

<table><thead><tr><th>Field</th><th>Description</th></tr></thead><tbody><tr><td>Detector</td><td>Detector(s) to use for resource detection. Available detectors include <code>aks</code>, <code>azure</code>, <code>consul</code>, <code>ec2</code>, <code>eks</code>, <code>gcp</code>, <code>k8snode</code>, <code>openshift</code>, and <code>system</code>.</td></tr><tr><td>Override</td><td>Whether or not to overwrite existing resource attributes.</td></tr><tr><td>Timeout</td><td>Time duration after which a resource detector request will timeout.</td></tr><tr><td>Hostname Source</td><td>When the <code>system</code> detector is in use, specifies the source used to detect the system hostname. Options include <code>os</code>, <code>dns</code>, <code>cname</code>, and <code>lookup</code>.</td></tr><tr><td>EC2 Tags</td><td>Specifies a list of regex's to match to EC2 instance tag keys that will be added as resource attributes to processed data.</td></tr><tr><td>K8s Node Environment Variable</td><td>The K8s node environment variable that has the node name to retrieve metadata for. Defaults to "KUBE\_NODE\_NAME" because the Bindplane Collector has this automatically set.</td></tr><tr><td>Consul Address</td><td>The address of the Consul server. If unset, the environment variable "CONSUL\_HTTP\_ADDR" will be used if it exists.</td></tr><tr><td>Consul Authentication</td><td>The type of authentication to use with Consul. One of 'Token' or 'Token File' is required if Consul's ACL System is enabled. Options are "None", "Token", or "Token File".</td></tr><tr><td>Consul Token</td><td>Token is used to provide a per-request ACL token which overrides the collector's default token. If unset, the environment variable "CONSUL\_HTTP\_TOKEN" will be used if it exists.</td></tr><tr><td>Consul Token File</td><td>Token File is a file containing the current token to use for this client. If provided, it is read once at startup and never again. If unset, the environment variable "CONSUL\_HTTP\_TOKEN\_FILE" will be used if it exists.</td></tr><tr><td>Consul Datacenter</td><td>Optional Consul Datacenter to use. If not provided, the default collector datacenter is used.</td></tr><tr><td>Consul Namespace</td><td>Optional namespace to attach to each Consul request. If unset, the environment variable "CONSUL\_NAMESPACE" will be used if it exists.</td></tr><tr><td>Consul Metadata Labels</td><td>Allowlist of Consul Metadata keys to use as resource attributes.</td></tr></tbody></table>

<Note>
  Multiple detectors may be selected on a single processor. However, if multiple processors use a common attribute name, the first detector will have precedent. For more info, see this OTel [documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor#ordering).
</Note>