-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HAProxy saved objects won't import #9389
Comments
Pinging @elastic/infrastructure |
What is the exact file you moved? You can't take the file from the Github repo and move it into the package as the encoding is done during packaging. Closing as this should be fixed by #9313 |
@ruflin actually there is something wrong with this dashboard, let me take a look. |
@bigphilwa thanks for reporting this, there were actually some issues with this dashboard, I have opened #9417 to fix them. |
@jsoriano Thanks for double checking. |
@ruflin I moved the Filebeat-haproxy-overview.json that was in the Filebeat Windows zip package (filebeat-6.5.1-windows-x86_64.zip\filebeat-6.5.1-windows-x86_64\kibana\default\dashboard\Filebeat-haproxy-overview.json) The fix for me was as I stated...converted all nested json objects to text strings. Like the very beginning of the file for instance looks like this >
After changing it all to be like this > it worked (with the exception of the other two issues found after that).
|
After moving the Filebeat-haproxy-overview.json file to the correct location and running filebeat setup --dashboards, there is an error when the program trys to load the HAProxy json file. It seems that the nested json objects in the file are expected to be text fields and NOT json. All other modules work just fine and their json files all contain escaped json text strings instead of plain json. The following error is logged when running setup:
I've confirmed the saved objects (visualizations and dashboard) load without issue when I converted the objects to text strings. So not only that, but after the objects were loaded, I found two other issues noted below:
Please include configurations and logs if available.
s
For confirmed bugs, please report:
The text was updated successfully, but these errors were encountered: