-
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
Move the import/export dashboards scripts to dev-tools #1359
Move the import/export dashboards scripts to dev-tools #1359
Conversation
monicasarbu
commented
Apr 8, 2016
- Add bash and powershell script to the beats/dev-tools repo
- Add script to export the dashboards and its dependencies for a single Beat
- Add docs
|
||
KIBANA_ES?=http://localhost:9200/ | ||
.PHONY: update | ||
kibana-export: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea to have it here was to make it easily available for community beats developers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I will them back in the Makefile once I check the add details about how to use the new script.
4e68e6d
to
0ba4af1
Compare
8847c0b
to
daeafa3
Compare
[[new-dashboards]] | ||
== Developer Guide: Creating new Kibana dashboards | ||
|
||
This guide walks you through the steps for creating a new Kibana dashboards |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should recommend here to use the virtual environment under testing/environments
to create the dashboards. The reasons for this is:
- People start with an empty Kibana instance
- Everyone is using the same Kibana version (most recent one)
- No setup on developer side needed
This should lead to hopefully cleaner dashboards or outdated dashboards.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point. I will add it.
LGTM. What happens with the "general" files in libbeat? https://github.com/elastic/beats/tree/master/libbeat/etc/kibana Are these still taken into account or not needed anymore? |
@ruflin Good point. I didn't notice those from libbeat. I think we can delete the etc/kibana from libbeat as there are no common widgets or searches. |
@monicasarbu Previously we had the Navigation one in all dashboards. So this is not the case anymore? |
The Navigation widget should be added only to the Beats that have more than one Kibana dashboard to make it easier to navigate between them. |
- Add bash/powershell scripts to import and export the dashboards and its dependencies in Kibana. - Run `make import-dashboards` in a Beat repository to import all the dashboards and its dependencies from etc/kibana to Elasticsearch - Run `make export-dashboards` in a Beat repository to export all the dashboards and its dependencies from etc/kibana to Elasticsearch - Add documentation - Update changelog - Recommend to use testing/environments when creating dashboards.
56c8d55
to
ef86371
Compare
All the comments are addressed. |