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.

Sign up for GitHub

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

Jump to bottom

[ResponseOps] alerting telemetry task throwing validation error on count_mw_total #194717

Closed
pmuellr opened this issue Oct 2, 2024 · 1 comment · Fixed by #194827
Closed

[ResponseOps] alerting telemetry task throwing validation error on count_mw_total #194717

pmuellr opened this issue Oct 2, 2024 · 1 comment · Fixed by #194827
Assignees
@guskovaue
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@pmuellr
Copy link
Member

pmuellr commented Oct 2, 2024

Seen in serverless logs:

Task (alerting_telemetry/Alerting-alerting_telemetry) has a validation error: [count_mw_total]: expected value of type [number] but got [undefined] (no stack trace)

Looks like it may have started with this PR: #192483 ; looks like the field was added then, and the merge date seems to at least somewhat correlate when the errors started getting logged.
@pmuellr pmuellr added bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Oct 2, 2024
@elasticmachine
Copy link
Contributor

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

@guskovaue guskovaue self-assigned this Oct 2, 2024
@pmuellr pmuellr mentioned this issue Oct 3, 2024
Merged
@guskovaue guskovaue linked a pull request Oct 4, 2024 that will close this issue
[ResponseOps][Telemetry] Add default value for new telemetry fields for old tasks #194827
Merged
guskovaue added a commit that referenced this issue Oct 4, 2024
@guskovaue
[ResponseOps][Telemetry] Add default value for new telemetry fields f…
38abda5 
…or old tasks (#194827)

Solve: #194717

When we add new fields to telemetry, we forgot to add them to this
place, which for tasks that were created < 8.10 will go migration.
Probably serverless has some old tasks. Probably because of it task run
fails. So I fix it here.
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Oct 4, 2024
@guskovaue
[ResponseOps][Telemetry] Add default value for new telemetry fields f…
124660d 
…or old tasks (elastic#194827)

Solve: elastic#194717

When we add new fields to telemetry, we forgot to add them to this
place, which for tasks that were created < 8.10 will go migration.
Probably serverless has some old tasks. Probably because of it task run
fails. So I fix it here.

(cherry picked from commit 38abda5)
tiansivive pushed a commit to tiansivive/kibana that referenced this issue Oct 7, 2024
@guskovaue @tiansivive
[ResponseOps][Telemetry] Add default value for new telemetry fields f…
6823f2b 
…or old tasks (elastic#194827)

Solve: elastic#194717

When we add new fields to telemetry, we forgot to add them to this
place, which for tasks that were created < 8.10 will go migration.
Probably serverless has some old tasks. Probably because of it task run
fails. So I fix it here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@guskovaue guskovaue

Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ResponseOps][Telemetry] Add default value for new telemetry fields for old tasks guskovaue/kibana
3 participants
@pmuellr @elasticmachine @guskovaue