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

[FR] CI Job to Sync ES|QL Custom Fields with Prebuilt Filterlist for Telemetry #4168

Open
terrancedejesus opened this issue Oct 17, 2024 · 3 comments
Labels

Comments

@terrancedejesus
Copy link
Contributor

terrancedejesus commented Oct 17, 2024

Repository Feature

Core Repo - (rule management, validation, testing, lib, cicd, etc.)

Problem Description

At the moment, when using ES|QL for writing detection rule queries, often we use aggregate functions, eval or pre-processing functions (grok and dissect) to create useful fields for our filters.

In this instance, those fields are not available in global alert telemetry, which relies on a static filterlist for determining what fields to ingest from the alerts.

Desired Solution

As such, we must develop a CI job that loads the ES|QL rules, reviews custom fields and adds those to the filterlist. The CI job would run on merges into main only.

Considered Alternatives

No alternatives considered. This suggestion is post conversation with Security Data Analytics team.

Additional Context

Related to https://github.com/elastic/ia-trade-team/issues/101

@terrancedejesus terrancedejesus added enhancement New feature or request Team: TRADE labels Oct 17, 2024
@Mikaayenson
Copy link
Contributor

We will need to consider how to handle the internal list in CI. We may want to kickoff a job that runs in CI in a different repo.

@botelastic
Copy link

botelastic bot commented Dec 16, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the stale 60 days of inactivity label Dec 16, 2024
@botelastic
Copy link

botelastic bot commented Dec 23, 2024

This has been closed due to inactivity. If you feel this is an error, please re-open and include a justifying comment.

@botelastic botelastic bot closed this as completed Dec 23, 2024
@Mikaayenson Mikaayenson reopened this Jan 24, 2025
@botelastic botelastic bot removed the stale 60 days of inactivity label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants