# Kibana plugin development inspect

**URL:** <https://discuss.elastic.co/t/kibana-plugin-development-inspect/212244>\
**Category:** Kibana\
**Created:** [December 18, 2019, 1:35am UTC](https://discuss.elastic.co/t/kibana-plugin-development-inspect/212244 "2019-12-18T01:35:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![McKittrick\_Kaminski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mckittrick_kaminski/32/59595_2.png) [@McKittrick\_Kaminski](https://discuss.elastic.co/u/McKittrick_Kaminski)\
**Post date:** [December 18, 2019, 1:35am UTC](https://discuss.elastic.co/t/kibana-plugin-development-inspect/212244/1 "2019-12-18T01:35:15Z")

</div>

So I'm trying to debug a plugin thats getting an error, but I'm having trouble launching Kibana with inspection and connecting to it.

I've seen in the contributing docs that I can use `yarn debug` to launch kbn with debugging ports, but there's not option for that within the plugin, using plugin-helpers. `watch netstat -tulpn` doesn't show any of the 9229, 9230, or 9231 ports listening.

Also, 9229 seems to attach to the process running the elasticsearch snapshot.

How do I get kibana to open up an inspect port for a plugin I'm developing, so that I can connect to it with vscode?

### EDIT

I seem to have figured it out. If you run `yarn debug` from the kibana directory, rather than the kibana/plugins/my\_plugin directory, it will launch the correct listening ports _and_ it will link your plugin in. I assumed that you had to run the yarn commands from inside the plug directory, but thats not true.

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [December 18, 2019, 7:04pm UTC](https://discuss.elastic.co/t/kibana-plugin-development-inspect/212244/2 "2019-12-18T19:04:21Z")

</div>

Thanks for keeping us posted.

Cheers,  
Bhavya

---

<div class="post-metadata">

**Author:** ![McKittrick\_Kaminski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mckittrick_kaminski/32/59595_2.png) [@McKittrick\_Kaminski](https://discuss.elastic.co/u/McKittrick_Kaminski)\
**Post date:** [December 18, 2019, 8:01pm UTC](https://discuss.elastic.co/t/kibana-plugin-development-inspect/212244/3 "2019-12-18T20:01:51Z")

</div>

Obvious feedback here is that it would be nice if the plugin-helpers had a `yarn debug` command that passed through to the `yarn debug` in the kibana project above that.

Should I open a ticket in the github?

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [December 18, 2019, 8:22pm UTC](https://discuss.elastic.co/t/kibana-plugin-development-inspect/212244/4 "2019-12-18T20:22:11Z")

</div>

That will be great. Here please: [https://github.com/elastic/kibana/issues](https://github.com/elastic/kibana/issues)

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 15, 2020, 8:28pm UTC](https://discuss.elastic.co/t/kibana-plugin-development-inspect/212244/5 "2020-01-15T20:28:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.