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] email action fails with no useful error message #62337

Closed
pmuellr opened this issue Apr 2, 2020 · 3 comments
Closed

[Alerting] email action fails with no useful error message #62337

pmuellr opened this issue Apr 2, 2020 · 3 comments
Assignees
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@pmuellr
Copy link
Member

pmuellr commented Apr 2, 2020

Kibana version: 7.7 build candidate

Elasticsearch version: "

Describe the bug:

Email action fails to run, reporting a failure in the Kibana.log, but not what the failure was.

As seen in logs:

2020-04-02T15:06:16Z [debug][taskManager]: Running task actions:.email 7ee7...
2020-04-02T15:06:16Z [error][taskManager]: Task actions:.email 7ee7... failed: Error: error sending email

Any additional context:

Customer thinks this is probably a configuration error on their smtp proxy.

I'm thinking there should have been a message from the actions plugin here, so a little concerned there wasn't. Should try to repro an error scenario like this and do a little debugging.

Even if the actions plugin did generate an error log message, not completely clear what it would write, since it would presumably have to trust that the error message from nodemailer was "safe" enough to write to the Kibana logs.

May also be a case where the event log would be a useful place to dump these 3rd party service error messages.

@pmuellr pmuellr added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Apr 2, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@pmuellr
Copy link
Member Author

pmuellr commented Nov 23, 2020

This should have been resolved by #79474 - my bad for not referencing it there.

But, good excuse to do a manual check that we are actually doing that. Assuming it works as intended, we can close this.

@ymao1 ymao1 self-assigned this Nov 30, 2020
@ymao1
Copy link
Contributor

ymao1 commented Dec 1, 2020

Confirmed that this was resolved by #79474

@ymao1 ymao1 closed this as completed Dec 1, 2020
@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

4 participants