[Response Ops][Connectors] Undefined message
#168871
Assignees
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Alerting/RuleActions
Issues related to the Actions attached to Rules on the Alerting Framework
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
ymao1
added
bug
|
Pinging @elastic/response-ops (Team:ResponseOps) |
|
We're seeing these on the Elasticsearch Datastore side of things; it appears that one particular alert (at least) is showing up this way every time it fires. |
github-project-automation
bot
moved this to Awaiting Triage
in AppEx: ResponseOps - Rules & Alerts Management
XavierM
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Rules & Alerts Management
Zacqary
moved this from Todo
to In Progress
in AppEx: ResponseOps - Rules & Alerts Management
|
I noticed https://github.com/elastic/apm-managed-service/issues/413 was closed because these alerts are no longer happening. @ymao1 @gwbrown do y'all know if this issue is still ongoing? Not sure where to start investigating. |
|
I did a search in slack and the last time we got this message was Oct 23, so maybe it's not an issue anymore? |
github-project-automation
bot
moved this from In Progress
to Done
in AppEx: ResponseOps - Rules & Alerts Management
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've been receiving alerts that look like this:
Using the connector execution logs to try to match up timestamps, it looks like it is coming from a slo.burnRate rule with a normal looking context message (just uses the default). We need to figure out why it's sending
undefinedand fix it.The text was updated successfully, but these errors were encountered: