From bb215ff34e676afdfdffa5fd60454a526f3afac9 Mon Sep 17 00:00:00 2001 From: Lorenzo Mangani Date: Sat, 3 Feb 2024 13:29:07 +0100 Subject: [PATCH] Update ingestion.md --- docs/profiling/ingestion.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/profiling/ingestion.md b/docs/profiling/ingestion.md index 2d32af2..0a9a411 100644 --- a/docs/profiling/ingestion.md +++ b/docs/profiling/ingestion.md @@ -25,15 +25,19 @@ The following protocol APIs are supported for ingesting continuous profiling eve Pyroscope is a continuous profiling format that allows you to analyze the performance of your applications.
Ingestion through the **qryn otel-collector** offers two primary methods: -![qryn_pyroscope_flow](https://github.com/metrico/qryn-docs/assets/1423657/e1d4232a-d2c4-467d-8b34-fae0ca95b42e) - - #### SDK Instrumentation The Pyroscope SDKs provide you with the capability to directly instrument your application, enabling more accurate profiling. This feature is particularly useful when you desire complete control over the profiling process or when your application is written in a language supported by the SDKs, such as _Java, Python, .NET, and more_. #### Auto-Instrumentation [Grafana Agent](https://grafana.com/docs/pyroscope/latest/configure-client/grafana-agent/go_pull/) can run alongside your application to collect profiling data at regular intervals. With the **eBPF** profiling option, things get even easier as there's no need for pull or push mechanisms. +#### Ingestion +Both methods use the qryn [otel-collector](https://github.com/metrico/otel-collector) to ingest data to the database + +![qryn_pyroscope_flow](https://github.com/metrico/qryn-docs/assets/1423657/e1d4232a-d2c4-467d-8b34-fae0ca95b42e) + + + ## ** OTEL Collector **