# Import new search to kibana via command line

**URL:** <https://discuss.elastic.co/t/import-new-search-to-kibana-via-command-line/82028>\
**Category:** Elasticsearch\
**Created:** [April 11, 2017, 5:40pm UTC](https://discuss.elastic.co/t/import-new-search-to-kibana-via-command-line/82028 "2017-04-11T17:40:25Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jkuang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkuang/32/72637_2.png) [@jkuang](https://discuss.elastic.co/u/jkuang)\
**Post date:** [April 12, 2017, 12:18am UTC](https://discuss.elastic.co/t/import-new-search-to-kibana-via-command-line/82028/7 "2017-04-12T00:18:49Z")

</div>

I'm still a bit confused on what you mean by Kibana searches. Like using the Dev Tool to run queries or the Kibana visualization.

If it's the Kibana visualization , according to the discussion link :

> [@How to create visualization on the fly using a script](https://discuss.elastic.co/t/how-to-create-visualization-on-the-fly-using-a-script/31255/2):
>
> Most of the parameters you need to create visualizations and dashboards are stored in the URL state in Kibana 4. After creating a sample vis or dashboard, you should be able to examine the URL and decide what to parameterize.

Yes, you have to test it yourself to figure the params. It does not cover how.

---

_[View the full topic](https://discuss.elastic.co/t/import-new-search-to-kibana-via-command-line/82028)._