# Using instrumentation libraries

> How to instrument libraries an app depends on

---

When you develop an app, you might use third-party libraries and frameworks to
accelerate your work. If you then instrument your app using OpenTelemetry, you
might want to avoid spending additional time to manually add traces, logs, and
metrics to the third-party libraries and frameworks you use.

Many libraries and frameworks already support OpenTelemetry or are supported
through OpenTelemetry
[instrumentation](/docs/concepts/instrumentation/libraries/), so that they can
generate telemetry you can export to an observability backend.

If you are instrumenting an app or service that use third-party libraries or
frameworks, follow these instructions to learn how to use natively instrumented
libraries and instrumentation libraries for your dependencies.

## Use natively instrumented libraries

If a library comes with OpenTelemetry support by default, you can get traces,
metrics, and logs emitted from that library by adding and setting up the
OpenTelemetry SDK with your app.

The library might require some additional configuration for the instrumentation.
Go to the documentation for that library to learn more.
{{__hugo_ctx/}}






> [!IMPORTANT] Help wanted
>
> As of today, we don't know about any Rust library that has
> OpenTelemetry natively integrated. If you are aware of such a library, [let us
> know][new-issue].





[new-issue]:
  https://github.com/open-telemetry/opentelemetry.io/issues/new/choose
{{__hugo_ctx/}}



## Use Instrumentation Libraries

Each instrumentation library is a [crate](https://crates.io/).

For example, the
[instrumentation library for Actix Web](https://crates.io/crates/opentelemetry-instrumentation-actix-web)
will automatically create [spans](/docs/concepts/signals/traces/#spans) and
[metrics](/docs/concepts/signals/metrics/) based on the inbound HTTP requests.

For a list of available instrumentation libraries, see the
[registry](/ecosystem/registry/?language=rust&component=instrumentation).