Skip to content
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

Merged

Conversation

monicasarbu
Copy link
Contributor

  • 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:
Copy link
Contributor

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.

Copy link
Contributor Author

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.

@monicasarbu monicasarbu force-pushed the move_import_export_dashboards_scripts branch from 4e68e6d to 0ba4af1 Compare April 8, 2016 20:02
@monicasarbu monicasarbu force-pushed the move_import_export_dashboards_scripts branch from 8847c0b to daeafa3 Compare April 11, 2016 08:48
[[new-dashboards]]
== Developer Guide: Creating new Kibana dashboards

This guide walks you through the steps for creating a new Kibana dashboards
Copy link
Contributor

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.

Copy link
Contributor Author

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.

@ruflin
Copy link
Contributor

ruflin commented Apr 11, 2016

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?

@monicasarbu
Copy link
Contributor Author

@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.

@ruflin
Copy link
Contributor

ruflin commented Apr 12, 2016

@monicasarbu Previously we had the Navigation one in all dashboards. So this is not the case anymore?

@monicasarbu
Copy link
Contributor Author

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.
@monicasarbu monicasarbu force-pushed the move_import_export_dashboards_scripts branch from 56c8d55 to ef86371 Compare April 12, 2016 22:04
@monicasarbu
Copy link
Contributor Author

All the comments are addressed.

@ruflin ruflin merged commit 5cfb20c into elastic:master Apr 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants