Skip to content
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

[DOC] Update security analytics detector creation to include data streams and aliases #6141

Closed
1 of 4 tasks
jowg-amazon opened this issue Jan 13, 2024 · 0 comments · Fixed by #6284
Closed
1 of 4 tasks
Assignees
Labels
3 - Done Issue is done/complete v2.12.0
Milestone

Comments

@jowg-amazon
Copy link

jowg-amazon commented Jan 13, 2024

What do you want to do?
In 2.12 security analytics now officially supports detectors to be configured on data streams and index aliases. Previously we only officially supported detectors to run against index patterns but they can now be configured using data streams and index aliases as well. We want to add documentation in the creating detectors page to include the fact that they can define a Data source as a data stream or an index alias now.

When a detector is configured on an alias or a data stream, the detector only considers the current write index. Aliases may be searchable or writable aliases. If the detector is configured against a searchable alias, the detectors will not run on any data. We also want to mention in the documentation that if a detector is configured on an alias, they should ingest data via the alias and not the concrete index directly.

It may be helpful to also point them to existing documentation about Index alias and data streams:

Related PR:

Tell us about your request. Provide a summary of the request and all versions that are affected.

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

@hdhalter hdhalter added v2.12.0 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Jan 16, 2024
@hdhalter hdhalter added this to the v2.12 milestone Jan 16, 2024
@hdhalter hdhalter added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. labels Jan 23, 2024
@Naarcha-AWS Naarcha-AWS added 3 - Tech review PR: Tech review in progress and removed 2 - In progress Issue/PR: The issue or PR is in progress. labels Jan 29, 2024
@hdhalter hdhalter added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 3 - Tech review PR: Tech review in progress labels Jan 29, 2024
@hdhalter hdhalter added the 3 - Done Issue is done/complete label Feb 8, 2024
@hdhalter hdhalter closed this as completed Feb 8, 2024
@hdhalter hdhalter removed the 2 - In progress Issue/PR: The issue or PR is in progress. label Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Done Issue is done/complete v2.12.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants