Cherry-pick #20150 to 7.10: Log debug message if the Kibana dashboard can not be imported #22761
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ed from the archive (elastic#12211) (elastic#20150) There is a predefined combination of directory structure and setup.dashboards.beat property that has to be defined to successfully import dashboards to the Kibana. Co-authored-by: dplavcic <dalibor.plavcic@gmail.com> (cherry picked from commit c2bb3f0)
|
Pinging @elastic/integrations-services (Team:Services) |
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures
|
| Test | Results |
|---|---|
| Failed | 1 |
| Passed | 16523 |
| Skipped | 1382 |
| Total | 17906 |
Genuine test errors 
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Build&Test / metricbeat-goIntegTest / TestFetch – status
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #20150 to 7.10 branch. Original message:
This PR is the updated verion of a community contribution which was abandoned in #13387. The original PR description is the following:
As described in #12211, depending on the value of setup.dashboards.beat there is a required directory structure for successful import of the Kibana dashboards from the archive file.
This PR adds additional path in case when no Kibana dashboards can be imported from the archive file, which logs debug message as shown below:
Implementation of point 2 from #12211 proposal.
There is a table in #12211 that contains test cases for this issue, but I currently don't know how to mock all necessary dependencies and implement unit tests for this without too much changes in libbeat/dashboards/importer.go.
I see that there are some integration tests for loading dashboards in libbeat/tests/system/test_dashboard.py so I'll check those out.
Fixes #12211
Closes #13387