-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Attaching screenshot to the browser monitoring alert #154575
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
@shanisagiv1 what do you think? |
I'm missing some context.
Screenshots of what? And what is a "browser monitoring alert". We have some issues open talking about being able to embed images in some of the notification services (email / slack). Presumably the images would be provided by the rules, somehow, and display something like the preview graphs that some rule types display in their editor. Is there anything new/different here? |
Yes, exactly this. Didn't find it on the community forum |
Sorry for my late reply here. Thanks for the additional context. As Patrick said we do have some plans to improve the existing experience when triggering an action to a connector like an email/slack and in particular attachments. can you verify that the following ER is the same use case? Thanks @upcFrost |
Im getting 404 on this link. It sounds pretty similar though. My only concern is that if this feature is limited by the connector type, it might not work well with two-stage alerts (first write to "alerts" index, then send alert from this index) |
Describe the feature:
It would be great to be able to attach screenshots to browser monitoring alerts.
Describe a specific use case for the feature:
The use case is to see which step failed without logging into kibana (which might be behind corp VPN which might require 2FA to connect which will require laptop/mobile with the token generator etc). Very helpful for alerts on slack and similar messengers. It quickly provides some very basic assessment of the situation as in "how dead are we".
The text was updated successfully, but these errors were encountered: