-
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
Addressing multiple dashboard issues: deps loading once, field conversion, etc. #27669
Conversation
Pinging @elastic/agent (Team:Agent) |
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.
Tested locally and works for me. 👍
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Steps errorsExpand to view the steps failures
|
Test | Results |
---|---|
Failed | 0 |
Passed | 53771 |
Skipped | 5325 |
Total | 59096 |
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.
👍
…sion, etc. (#27669) This PR addresses 3 minor issues in dashboard loading: 1. Everything should be loaded once 2. Some fields have to be strings that were objects before 3. Replacing index names in dashboards is no longer an NDJSON This prevented setup from working properly. (cherry picked from commit 42ca950)
…sion, etc. (#27669) This PR addresses 3 minor issues in dashboard loading: 1. Everything should be loaded once 2. Some fields have to be strings that were objects before 3. Replacing index names in dashboards is no longer an NDJSON This prevented setup from working properly. (cherry picked from commit 42ca950)
…sion, etc. (#27669) (#27682) This PR addresses 3 minor issues in dashboard loading: 1. Everything should be loaded once 2. Some fields have to be strings that were objects before 3. Replacing index names in dashboards is no longer an NDJSON This prevented setup from working properly. (cherry picked from commit 42ca950) Co-authored-by: Noémi Ványi <kvch@users.noreply.github.com>
…sion, etc. (#27669) (#27683) This PR addresses 3 minor issues in dashboard loading: 1. Everything should be loaded once 2. Some fields have to be strings that were objects before 3. Replacing index names in dashboards is no longer an NDJSON This prevented setup from working properly. (cherry picked from commit 42ca950) Co-authored-by: Noémi Ványi <kvch@users.noreply.github.com>
* master: Forward port 7.14.1 changelog to master (elastic#27687) Addressing multiple dashboard issues: deps loading once, field conversion, etc. (elastic#27669) Remove adaptive queue sizes from agent's spec files (elastic#27653) Osquerybeat: Improve testability and unit test coverage (elastic#27591) Osquerybeat: lockdown flagsfile, prevent global defaults (elastic#27611) Import the references of dashboard assets using the Saved Objects API (elastic#27647) Fix bug with override path in cgroups (elastic#27620) Allow Kibana client to authorize with Elasticsearch API key (elastic#27540) Filebeat auditd: Fix Top Exec Commands dashboard visualization (elastic#27638) [elastic-agent] Fix docker tar.gz generation for complete image (elastic#27621) Follow up changes in dashboards in mage check && fix minor issue (elastic#27553) [Heartbeat] Fix bug where `enabled: false` is ignored. (elastic#27615) Support kube_state_metrics v2.0.0 (elastic#27552)
…sion, etc. (elastic#27669) ## What does this PR do? This PR addresses 3 minor issues in dashboard loading: 1. Everything should be loaded once 2. Some fields have to be strings that were objects before 3. Replacing index names in dashboards is no longer an NDJSON ## Why is it important? This prevented setup from working properly.
What does this PR do?
This PR addresses 3 minor issues in dashboard loading:
Why is it important?
This prevented setup from working properly.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.