# Questions on Graph

**URL:** <https://discuss.elastic.co/t/questions-on-graph/116270>\
**Category:** Kibana\
**Tags:** elastic-stack-graph\
**Created:** [January 19, 2018, 4:00pm UTC](https://discuss.elastic.co/t/questions-on-graph/116270 "2018-01-19T16:00:14Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [January 24, 2018, 3:33pm UTC](https://discuss.elastic.co/t/questions-on-graph/116270/4 "2018-01-24T15:33:12Z")

</div>

> [@David\_Tomasheski](#):
>
> i was hoping for an iframe type object.

For now there's a manual hack you can use - see [Iframe to graph - #2 by Mark\_Harwood](https://discuss.elastic.co/t/iframe-to-graph/83089/2)

> [@David\_Tomasheski](#):
>
> that brings me to two new questions about the url drill down in particular.

For fancier drill-down integrations you may need to introduce some sort of custom proxy to redirect as appropriate. The Graph URL drill-down templates can use a variety of param encodings so if you use the RISON encoded query dsl that should pass the JSON from which you can parse out field names and terms from the URL. You'd then need to redirect as appropriate to the target system using a POST or whatever URL encoding is required for the target system and the parsed terms.

---

_[View the full topic](https://discuss.elastic.co/t/questions-on-graph/116270)._