# HAProxy dashboard, error loading

**URL:** <https://discuss.elastic.co/t/haproxy-dashboard-error-loading/159398>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 4, 2018, 4:42pm UTC](https://discuss.elastic.co/t/haproxy-dashboard-error-loading/159398 "2018-12-04T16:42:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bigphil](https://avatars.discourse-cdn.com/v4/letter/b/65b543/32.png) [@bigphil](https://discuss.elastic.co/u/bigphil)\
**Post date:** [December 4, 2018, 4:42pm UTC](https://discuss.elastic.co/t/haproxy-dashboard-error-loading/159398/1 "2018-12-04T16:42:09Z")

</div>

Using Filebeat 6.5.1:  
After moving the HAProxy dashboard object to "..\kibana\6\dashboard\Filebeat-haproxy-overview.json" and attempting to run filebeat setup --dashboards, the following error occurs \>

> 2018-12-04T08:25:35.822-0800 ERROR instance/beat.go:800 Exiting: Error importing Kibana dashboards: fail to import the dashboards in Kibana: Error importing directory C:\ELASTIC\filebeat-6.5.1-windows-x86\_64\kibana: Failed to import dashboard: Failed to load directory C:\ELASTIC\filebeat-6.5.1-windows-x86\_64\kibana/6/dashboard:  
> error loading C:\ELASTIC\filebeat-6.5.1-windows-x86\_64\kibana\6\dashboard\Filebeat-haproxy-overview.json: failed to parse field [visualization.kibanaSavedObjectMeta.searchSourceJSON] of type [text]. Response: {"objects":[{"id":"55251360-aa32-11e8-9c06-877f0445e3e0","type":"visualization","error":{"message":"failed to parse field [visualization.kibanaSavedObjectMeta.searchSourceJSON] of type [text]"}},{"id":"7fb671f0-aa32-11e8-9c06-877f0445e3e0","type":"vi... (truncated)

Any ideas? Has anyone imported the HAProxy dashboard successfully? All other dashboards and objects import successfully.

---

<div class="post-metadata">

**Author:** ![bigphil](https://avatars.discourse-cdn.com/v4/letter/b/65b543/32.png) [@bigphil](https://discuss.elastic.co/u/bigphil)\
**Post date:** [December 4, 2018, 6:15pm UTC](https://discuss.elastic.co/t/haproxy-dashboard-error-loading/159398/2 "2018-12-04T18:15:32Z")

</div>

This seems like a bug to me. I converted all of the searchSourceJSON objects to type text and it then got past that error, but now fails on uiStateJSON object. After looking at all of the other module json files, HAProxy is the _only_ one that uses pure json in the config. The others use text for the following objects: searchSourceJSON, uiStateJSON, viState, optionsJSON, panelsJSON, (seemingly any nested json objects). It seems the filebeat parser is expecting text here instead.

---

<div class="post-metadata">

**Author:** ![bigphil](https://avatars.discourse-cdn.com/v4/letter/b/65b543/32.png) [@bigphil](https://discuss.elastic.co/u/bigphil)\
**Post date:** [December 5, 2018, 12:38am UTC](https://discuss.elastic.co/t/haproxy-dashboard-error-loading/159398/3 "2018-12-05T00:38:11Z")

</div>

Fixed by converting all nested json objects to text strings. Found a couple other issues and will post a bug report on github.

---

<div class="post-metadata">

**Author:** ![bigphil](https://avatars.discourse-cdn.com/v4/letter/b/65b543/32.png) [@bigphil](https://discuss.elastic.co/u/bigphil)\
**Post date:** [December 5, 2018, 12:55am UTC](https://discuss.elastic.co/t/haproxy-dashboard-error-loading/159398/4 "2018-12-05T00:55:32Z")

</div>

bug filed [here](https://github.com/elastic/beats/issues/9389)

---

<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 2, 2019, 12:55am UTC](https://discuss.elastic.co/t/haproxy-dashboard-error-loading/159398/5 "2019-01-02T00:55:37Z")

</div>

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