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

[Telemetry] Move indices metadata out of security solution #212875

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

szaffarano
Copy link
Contributor

@szaffarano szaffarano commented Mar 3, 2025

Summary

This POC makes the indices metadata telemetry feature available on observability clusters.

The goal is to test how it works by porting the logic outside the security solutions plugin. I'm unsure whether the target plugin, metrics_data_access, is ok or we should move the code to another plugin or create a new one.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

POC to make the indices metadata telemetry feature available for observability
@elasticmachine
Copy link
Contributor

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

  • Click to trigger kibana-pull-request for this PR!
  • Click to trigger kibana-deploy-project-from-pr for this PR!
  • Click to trigger kibana-deploy-cloud-from-pr for this PR!

@szaffarano szaffarano changed the title Move indices metadata out of security solution [Telemetry] Move indices metadata out of security solution Mar 3, 2025
@szaffarano szaffarano self-assigned this Mar 3, 2025
@szaffarano szaffarano added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. ci:project-deploy-observability Create an Observability project labels Mar 3, 2025
Copy link
Contributor

github-actions bot commented Mar 3, 2025

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@szaffarano
Copy link
Contributor Author

/oblt-deploy

@szaffarano
Copy link
Contributor Author

/oblt-deploy

@szaffarano
Copy link
Contributor Author

/ci

@szaffarano
Copy link
Contributor Author

/ci

@elasticmachine
Copy link
Contributor

elasticmachine commented Mar 5, 2025

💔 Build Failed

  • Buildkite Build
  • Commit: 9c8a4ee
  • Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-212875-9c8a4eed5277

Failed CI Steps

Metrics [docs]

✅ unchanged

History

cc @szaffarano

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci:project-deploy-observability Create an Observability project Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants