Replace Markdown Navigation with Links Panel - #14938
Conversation
🚀 Benchmarks reportTo see the full report comment with |
| @@ -0,0 +1,14 @@ | |||
| { | |||
There was a problem hiding this comment.
Do these tag files need to be committed? I'm not actually sure how it works, but I thought that a kibana/tags.yml specified what tags to apply the dashboards, but we didn't need to commit the actual saved objects.
There was a problem hiding this comment.
While not completely sure, I deleted the tags and try to build the packages without the tags using elastic-package build.
It fails for all three of the packages that had tags removed (cisco_ise, fortinet_fortimail, and osquery).
|
As a note this ticket has been updated with the context from last iteration development meeting so modify some of the filtering behaviours. |
💚 Build Succeeded
History
|
|
|
Package cisco_ise - 1.29.0 containing this change is available at https://epr.elastic.co/package/cisco_ise/1.29.0/ |
|
Package fortinet_fortimail - 2.16.0 containing this change is available at https://epr.elastic.co/package/fortinet_fortimail/2.16.0/ |
|
Package imperva - 1.8.0 containing this change is available at https://epr.elastic.co/package/imperva/1.8.0/ |
|
Package osquery - 1.24.0 containing this change is available at https://epr.elastic.co/package/osquery/1.24.0/ |
Replaced markdown navigation in the cisco_ise, fortinet_fortimail, and osquery dashboards with link panels. Updated the supported Kibana version for the fortinet_fortimail integration to 8.11.0^. Removed the single redundant navigation link for the imperva integration dashboard.




Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
Built links panels for osquery and Cisco ISE to match the marked down before exactly in their kibana version.
Removed redundant information and links for imperva dashboard as discussed in #14812
Reviewed change logs and updated support for fortinet_fortimail to support kibana 8.11.0^ so we can add links panels.
Added links panels to fortinet_fortimail dashboard.
How to test this PR locally
Clone integrations repo.
Install elastic package locally.
Start elastic stack using elastic-package.
Install and test the packages locally with elastic-package
Go to dashboards and view the changes
Related issues
Closes #14812
Screenshots
Cisco ISE before:


Cisco ISE after
Osquery before:


Osquery after:


Fortinet Mail before:




Fortinet Mail after:




Imperva before. The integrations link is a relative link leading to the install integration page that can't be done in links panels. There is no navigation needed since it is only 1 dashboard page:


Imperva after: