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

[Alerting][Telemetry] Investigate what transformations are applied to alerting telemetry #123275

Closed
ymao1 opened this issue Jan 18, 2022 · 2 comments
Labels
Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) telemetry Issues related to the addition of telemetry to a feature

Comments

@ymao1
Copy link
Contributor

ymao1 commented Jan 18, 2022

Based on these comment

One thing to note is the telemetry team is able to perform transformations on the data in the "middle layer" of the process (which is basically a cloud service that sits in the middle of Kibana sending the data, and it being indexed into the ES cluster) so it's possible to fix any issues outside of our deployment model

The transformations are part of the new telemetry system we've been building out

We should investigate:

  • What, if any, transformations are currently being applied to alerting telemetry data
  • What, if any, transformations should we think about applying to alerting telemetry data. I would specifically start with the usage counter information that we're tracking but this could also apply to any alerting telemetry.
@ymao1 ymao1 added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework telemetry Issues related to the addition of telemetry to a feature labels Jan 18, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@mikecote
Copy link
Contributor

mikecote commented Sep 8, 2022

Closing as we've moved our telemetry to the response ops indexer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) telemetry Issues related to the addition of telemetry to a feature
Projects
None yet
Development

No branches or pull requests

4 participants