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

Unify Kibana dashboard directory logic across Beats #7265

Merged
merged 1 commit into from
Jun 11, 2018

Conversation

ruflin
Copy link
Member

@ruflin ruflin commented Jun 5, 2018

Currently all dashboards end up under _meta/kibana in each Beat. The problem with this directory is that for some Beats it contains the automatically collected and generated files and for others the original. This prevents us from having decoded JSON files for all dashboards across Beats.

An other benefit of having the kibana.generated directory is that now _meta/kibana can become the place for dashboards across modules in one Beat without having to worry about overwriting / removing these dashboards.

Community Beats must convert their dashboards with the script under #7224.

Further changes:

  • Decode Packetbeat and Winlogbeat dashboards
  • Move encoding step to libbeat so it is applied automatically to all dashboards in the kibana.generated directory.
  • Remove _meta/kibana from .gitignore as it can now be used to contain dashboards in all Beats.
  • Adjust Makefiles for the new logic.
  • Adjust tests to depend on kibana.generated directory

@ruflin ruflin added the in progress Pull request is currently in progress. label Jun 5, 2018
@ruflin ruflin force-pushed the kibana-dir-changes branch 4 times, most recently from b6e1535 to e10e130 Compare June 8, 2018 19:36
Currently all dashboards end up under `_meta/kibana` in each Beat. The problem with this directory is that for some Beats it contains the automatically collected and generated files and for others the original. This prevents us from having decoded JSON files for all dashboards across Beats.

An other benefit of having the `kibana.generated` directory is that now `_meta/kibana` can become the place for dashboards across modules in one Beat without having to worry about overwriting / removing these dashboards.

Community Beats must convert their dashboards with the script under elastic#7224.

Further changes:

* Decode Packetbeat and Winlogbeat dashboards
* Move encoding step to libbeat so it is applied automatically to all dashboards in the kibana.generated directory.
* Remove _meta/kibana from .gitignore as it can now be used to contain dashboards in all Beats.
* Adjust Makefiles for the new logic.
* Adjust tests to depend on kibana.generated directory
@ruflin ruflin added review libbeat :Dashboards and removed in progress Pull request is currently in progress. labels Jun 8, 2018
@ruflin ruflin changed the title Kibana directory changes Unify Kibana dashboard directory logic across Beats Jun 8, 2018
Copy link
Member

@jsoriano jsoriano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only one small comment

@@ -4,7 +4,7 @@ MAINTAINER Nicolas Ruflin <ruflin@elastic.co>
RUN set -x && \
apt-get update && \
apt-get install -y --no-install-recommends \
netcat python-pip virtualenv && \
netcat python-pip rsync virtualenv && \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rsync added but not used?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and now. It was used when make update was called inside the container. Now it happens outside again. The reason I would like to keep it in is that if someone wants to tests things from inside the container and run make update rsync will be needed for Filebeat.

@jsoriano jsoriano merged commit b3c5397 into elastic:master Jun 11, 2018
@ruflin ruflin deleted the kibana-dir-changes branch June 20, 2018 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants