Platforms
Sentry provides code-level observability that makes it easy to diagnose issues and learn continuously about your application code health. Data is captured by using an SDK within your application’s runtime. The Sentry team builds and maintains SDKs for most popular languages and frameworks, but there’s also a large ecosystem supported by the community.
If your use case is very specific, or not covered by Sentry, you'll find documentation on how to report events on your own using our SDK API.
It's considered bad practice to use Sentry SDKs in third-party plugins, packages, and libraries (such as payment SDKs or embeddable widgets) meant to be consumed by other apps. If an app uses a Sentry SDK in addition to a third-party package with its own Sentry SDK installed, the following issues can occur:
- Version conflicts.
- Signal handlers may overwrite each other, leading to one of the Sentry SDKs operating incorrectly.
- Third-party SDKs and libraries may leak users' PII data to the third-party's Sentry organization.
We also discourage using Sentry alongside other APM tools because it can lead to a number of side-effects that negatively impact performance and stability of the application.
All SDKs Supported by Sentry
If you use it, we probably support it.
These SDKs are maintained and supported by the Sentry community. While generally our community does a great job at responding to issues, it's important to understand that Sentry staff cannot help you with issues using a community-supported SDK.
- Clojure (Sentry Clj)
- Clojure (Raven Clj)
- Cloudflare Workers
- ColdFusion
- Crystal
- Defold
- Grails
- Hono
- Kubernetes
- Lua
- Nuxt 2
- OCaml
- Quarkus
- Scrapy
- Serverless Framework
- Strapi
- Terraform
- WordPress
Still can't find your favorite language or framework? Then we encourage you to consider writing your own SDK.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").