# đŸ›¶ Replacing Pyroscope with qryn + otel [![](https://grafana.com/docs/pyroscope/latest/logo.png align="center")](https://qryn.cloud) If you work with observability and continuous profiling you surely have already heard of, use and/or have tried **Grafana Pyroscope** > ***Grafana Pyroscope*** *is an open source software project for aggregating continuous profiling data. Continuous profiling is an observability signal that allows you to understand your workload’s resources (CPU, memory, etc.) usage down to the line number.* **Grafana** acquired **Pyroscope** and merged it with its **Phlare** continuous profiling database back in 2023. The smooth integration of **Grafana Pyroscope** with **Grafana** is one of its the main solution benefits allowing easy correlation of **continuous profiling** data with other observability signals, such as **metrics, logs,** and **traces**. *This is fantastic* until we get reminded Grafana products force their users to maintain completely different backends and datastores for their *"correlated"* products, pushing lots of complexity for opensource integrations and tedious management. So if you need logs, metrics, traces and profiling - *those are 4 parallel deployments.* This is where [**qryn**](https://qryn.dev) kicks in! One powerful stack, *fluent in all languages.* ### Another Pyroscope Our observability stack [**qryn**](https://qryn.dev) already offers native compatibility with **Grafana Loki, Mimir/Prometheus** and **Tempo** as part of its Polyglot API on top of OLAP databases and we're happy to announce **Pyroscope** API support has joined the family! Piece by piece, we integrated all the parts and protocols to make the integration work in qryn, with the generous cooperation of community resident **Tomer Shafir** ⭐ Profiling data now lives within the same OLAP database as logs, metrics and traces, providing integrators with full access and control for predictable cost/performance. *That's the polyglot* approach of **qryn**. [*More features. Less services. One datastore.*](https://qryn.dev) ### Get Started Users and integrators of [**qryn 3.0**](https://qryn.dev) can already ingest **continuous profiling data** in their favourite OLAP database by using the [qryn **opentelemetry** collector](https://github.com/metrico/otel-collector) integration for java clients *(soon to be extended to support a broader scope of pprof clients)* and query profiling data in **Grafana** through the **Pyroscope Datasource** using *qryn's* APIs. [![](https://cdn.hashnode.com/res/hashnode/image/upload/v1705411909102/5085dca1-8bb8-43c0-bed2-a78dcad46e89.png align="center")](https://qryn.dev) The search and filtering experience are fully compatible the *original Pyroscope API*, and can be instantly used without any additional knowledge, plugins or hacks [![](https://cdn.hashnode.com/res/hashnode/image/upload/v1705485625334/ed6ce7a3-2935-4496-9b5d-f8dc2e20c5ac.gif align="center")](https://qryn.dev) ### UPDATE 08/2024 **qryn** is fully compatible with the **Pyroscope Explore App** in Grafana! ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1725749132907/487fd2a4-32c5-4a68-9110-6c527b39e413.gif align="center") With the opensource front being already on the way, the integration with [qryn.cloud](https://qryn.cloud) is up next with focus on total integration with all available [gigapipe](https://gigapipe.com) products, as well as any external customer resource through collectors and agents. *Watch this space!* ***Updated Workflow*** Here's the upcoming qryn workflow updated with Profiling Features. *To the future!* [![](https://cdn.hashnode.com/res/hashnode/image/upload/v1705494697945/e3711142-9aac-493f-814e-4fc00b32e8b8.gif align="center")](https://qryn.dev)