Generalize install instructions to adapt to ai4soc project - #14818
Conversation
🚀 Benchmarks reportTo see the full report comment with |
| ### Enable the integration in Elastic | ||
|
|
||
| 1. In Kibana navigate to **Management** > **Integrations**. | ||
| 1. In the top search bar in Kibana, search for **Integrations**. |
There was a problem hiding this comment.
Nice! This is universal across all deployments and nav types -- LGTM! 🙂
andrewkroh
added
Integration:elastic_security
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
efd6
left a comment
efd6
left a comment
There was a problem hiding this comment.
Doc changes LGTM, changelog needs change.
💚 Build Succeeded
History
cc @kgeller |
|
|
Package elastic_security - 0.3.2 containing this change is available at https://epr.elastic.co/package/elastic_security/0.3.2/ |
|
Package google_secops - 1.2.1 containing this change is available at https://epr.elastic.co/package/google_secops/1.2.1/ |
|
Package microsoft_sentinel - 1.2.1 containing this change is available at https://epr.elastic.co/package/microsoft_sentinel/1.2.1/ |
|
Package splunk - 0.5.1 containing this change is available at https://epr.elastic.co/package/splunk/0.5.1/ |
…4818) * genericizing install instructions to adapt to ai4soc project * fixing typo as well * fixing changelog entry numbers and description
5 participants
Proposed commit message
Updates the
[elastic_security, google_secops, microsoft_sentinel, splunk]install instruction to be more generic, so that they also work for the AI4SOC integrations page.Instead of specifying the Management section of the sidebar, that doesn't exist in the AI4SOC project, utilize the search bar.
Also fixed a tiny typo in the
google_secopsreadme.Checklist
I have verified that all data streams collect metrics or logs.changelog.ymlfile.I have verified that Kibana version constraints are current according to guidelines.I have verified that any added dashboard complies with Kibana's Dashboard good practicesRelated issues