[sentinel_one] Add unified alert data stream - #17304
Conversation
Vale Linting ResultsSummary: 9 warnings, 3 suggestions found
|
| File | Line | Rule | Message |
|---|---|---|---|
| packages/sentinel_one/docs/README.md | 2446 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'. |
| packages/sentinel_one/docs/README.md | 2449 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'. |
| packages/sentinel_one/docs/README.md | 2450 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'. |
| packages/sentinel_one/docs/README.md | 2480 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'. |
| packages/sentinel_one/docs/README.md | 2480 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'. |
| packages/sentinel_one/docs/README.md | 2550 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'. |
| packages/sentinel_one/docs/README.md | 2550 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'. |
| packages/sentinel_one/docs/README.md | 2592 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'. |
| packages/sentinel_one/docs/README.md | 2599 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'. |
💡 Suggestions (3)
| File | Line | Rule | Message |
|---|---|---|---|
| packages/sentinel_one/docs/README.md | 2494 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| packages/sentinel_one/docs/README.md | 2494 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| packages/sentinel_one/docs/README.md | 2571 | Elastic.WordChoice | Consider using 'open' instead of 'launch', unless the term is in the UI. |
The Vale linter checks documentation changes against the Elastic Docs style guide.
To use Vale locally or report issues, refer to Elastic style guide for Vale.
🚀 Benchmarks reportTo see the full report comment with |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
All the suggestions are about the description of fields in the README. So we can’t change the description of ECS fields or SentinelOne-provided fields. |
kcreddy
left a comment
There was a problem hiding this comment.
Can you also fix some of the vale linting comments
| ### How it works | ||
|
|
||
| This integration periodically queries the SentinelOne REST API to retrieve Activity, Agent, Alert, Application, Application Risk, Group, Threat and Threat Event logs. | ||
| This integration periodically queries the SentinelOne REST API to retrieve Activity, Agent, Alert, Application, Application Risk, Group, Threat, Threat Event and Unified Alert logs. |
There was a problem hiding this comment.
Oxford comma is appropriate here to disambiguate "(Threat Event) and (Unified Alert) logs" from "(Threat Event and Unified Alert) logs".
| This integration periodically queries the SentinelOne REST API to retrieve Activity, Agent, Alert, Application, Application Risk, Group, Threat, Threat Event and Unified Alert logs. | |
| This integration periodically queries the SentinelOne REST API to retrieve Activity, Agent, Alert, Application, Application Risk, Group, Threat, Threat Event, and Unified Alert logs. |
💚 Build Succeeded
History
|
|
Package sentinel_one - 2.4.0 containing this change is available at https://epr.elastic.co/package/sentinel_one/2.4.0/ |
…alert (#142648) This PR focuses on the short term solution which add the `logs-sentinel_one.unified_alert-*` indices under the `kibana_system` role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming [PR](elastic/integrations#17304). As it ships transform pipeline too hence read, write permissions are also required.
…alert (#142823) This PR focuses on the short term solution which add the `logs-sentinel_one.unified_alert-*` indices under the `kibana_system` role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming [PR](elastic/integrations#17304). As it ships transform pipeline too hence read, write permissions are also required. (cherry picked from commit eba47dd)
…alert (#142824) This PR focuses on the short term solution which add the `logs-sentinel_one.unified_alert-*` indices under the `kibana_system` role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming [PR](elastic/integrations#17304). As it ships transform pipeline too hence read, write permissions are also required. (cherry picked from commit eba47dd)
…alert (#142822) This PR focuses on the short term solution which add the `logs-sentinel_one.unified_alert-*` indices under the `kibana_system` role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming [PR](elastic/integrations#17304). As it ships transform pipeline too hence read, write permissions are also required. (cherry picked from commit eba47dd)
This data stream collects unified alert logs from the Singularity™ Operations Center platform via the Unified Alert Management GraphQL API. API documentation is available with login[1]. Test samples were derived from documentation and live data samples, which were subsequently sanitized. [1] https://usea1-partners.sentinelone.net/soc-docs/en/unified-alert-management-graphql-api.html
Proposed commit message
Checklist
changelog.ymlfile.How to test this PR locally
Related Issue