# Exporting Flamegraph or Method level Data from Universal Profiling

**URL:** <https://discuss.elastic.co/t/exporting-flamegraph-or-method-level-data-from-universal-profiling/378423>\
**Category:** Continuous Profiling\
**Tags:** flamegraphs, functions, stacktraces\
**Created:** [May 22, 2025, 1:38pm UTC](https://discuss.elastic.co/t/exporting-flamegraph-or-method-level-data-from-universal-profiling/378423 "2025-05-22T13:38:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pooja\_Gajaram](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pooja_gajaram/32/140684_2.png) [@Pooja\_Gajaram](https://discuss.elastic.co/u/Pooja_Gajaram)\
**Post date:** [May 22, 2025, 1:38pm UTC](https://discuss.elastic.co/t/exporting-flamegraph-or-method-level-data-from-universal-profiling/378423/1 "2025-05-22T13:38:24Z")

</div>

Hi Team ,

I'm currently using the Elastic Universal Profiling and can view the flamegraph visualization for methods. However , I would like to know:

1. Is there a way to export the flamegraph data (e.g., as raw data or JSON) for further analysis?
2. Is it possible to extract method level CPU Usage data , including percentage CPU time or sample count per method , outside UI like in indexes or something?
3. Are there any APIs or tools provided to programmatically access this profiling information?  
This data would help us with internal performance analysis and alerting

Thanks

---

<div class="post-metadata">

**Author:** ![Florian\_Lehner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/florian_lehner/32/97221_2.png) [@Florian\_Lehner](https://discuss.elastic.co/u/Florian_Lehner)\
**Post date:** [June 30, 2025, 11:01am UTC](https://discuss.elastic.co/t/exporting-flamegraph-or-method-level-data-from-universal-profiling/378423/2 "2025-06-30T11:01:57Z")

</div>

Hi @Pooja_Gajaram

The profiling data is distributed across various Elasticsearch indices.  
With `POST /_profiling/flamegraph` it is possible to query for data in JSON format, that builds the flamegraph in the UI. But the format of this JSON is proprietary, not officially supported and may change any time without notice.
