# Resources LLMS index: [llms.txt](/llms.txt) --- Um [recurso](/docs/concepts/resources/) representa a entidade que está gerando telemetria como atributos do recurso. Por exemplo, an OTP Release que está gerando telemetria e que está sendo executado em um _container_ no Kubernetes tem o nome de an OTP Release, um nome de _pod_, um _namespace_ e possivelmente um nome de _deployment_. Todos esses quatro atributos podem ser incluídos em um recurso. No seu _backend_ de observabilidade, você pode usar as informações de um recurso para refinar a investigação de comportamentos relevantes. Por exemplo, se seus dados de rastros ou métricas indicarem latência no seu sistema, você pode restringir a investigação para um determinado _container_, _pod_ ou _deployment_ do Kubernetes. {{__hugo_ctx/}} ## Using resource detectors Resource detectors fetch resource attributes from various sources. The default detectors use the OS environment variable `OTEL_RESOURCE_ATTRIBUTES` and the `opentelemetry` OTP application environment variable `resource`. The detectors to use is a list of module names and can be configured in the Application configuration:

%% sys.config
{opentelemetry, {resource_detectors, [otel_resource_env_var, otel_resource_app_env]}}

## runtime.exs
config :opentelemetry, resource_detectors: [:otel_resource_env_var, :otel_resource_app_env]

Or through the environment variable `OTEL_RESOURCE_DETECTORS`: ```sh OTEL_RESOURCE_DETECTORS=otel_resource_env_var,otel_resource_app_env ``` All resources detectors are protected with a timeout, in milliseconds, after which they return an empty value. This allows for resource detectors to do things like hit the network without potentially hanging the entire program indefinitely. The default is 5000 milliseconds and can be set with environment variable `OTEL_RESOURCE_DETECTOR_TIMEOUT` or Application variable `otel_resource_detector_timeout`. ## Adding resources with OS and OTP application environment variables With the two default resource detectors enabled you can set resource attributes either with the OS environment variable `OTEL_RESOURCE_ATTRIBUTES`: ```sh OTEL_RESOURCE_ATTRIBUTES="deployment.environment=development" ``` Alternatively, use the `resource` OTP application environment under the `opentelemetry` Application configuration of `sys.config` or `runtime.exs`:

%% sys.config
{opentelemetry, {resource, #{deployment => #{environment => <<"development">>}}}}

## runtime.exs
config :opentelemetry, resource: %{deployment: %{environment: "development" }}

Resource attributes in the `resource` OTP application environment variable are flattened and combined with `.`, so `#{deployment => #{environment => <<"development">> }` is the same as `#{'deployment.environment' => <<"development">>}`. ## Custom resource detectors Custom resource detectors can be created by implementing the [`otel_resource_detector` behaviour](https://hexdocs.pm/opentelemetry/1.3.0/otel_resource_detector.html#callbacks) which contains a single callback `get_resource/1` that returns an [`otel_resource`](https://hexdocs.pm/opentelemetry/1.3.0/otel_resource.html). Note that there are [semantic conventions](/docs/specs/semconv/resource/) defined for `resource` that should be followed if they apply when adding new resource attributes.