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

Please bring back the option to create segregated synthetic alert rules for each of our synthetic monitors. #175298

Closed
andrelrmarques opened this issue Jan 23, 2024 · 7 comments · Fixed by #186585
Closed

Please bring back the option to create segregated synthetic alert rules for each of our synthetic monitors. #175298

andrelrmarques opened this issue Jan 23, 2024 · 7 comments · Fixed by #186585
Assignees
@shahzad31
Labels
enhancement New value added to drive a business result Team:obs-ux-management Observability Management User Experience Team

Comments

@andrelrmarques
Copy link

Describe the feature:

In Elastic 8.9.x there was an option to create segregated synthetic alert rules for each of our synthetic monitors, if you navigate to Observability > Alerts > Manage Rules > Create Rule , where you would see the following options:

  • Uptime monitor status
  • Uptime TLS

This screenshot shows how that looked like:
20240122-120054-001

After Elastic 8.10.x, the option is not longer available.
By having it, we were able to create separate rules for specific monitors by appliing a simple filter.
This feature was removed and centralized on just one rule for all monitors starting at 8.10.x release.

Describe a specific use case for the feature:
We need to send different alert descriptions for each synthetic monitor, and cannot do it using the current way
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 23, 2024
@jughosta jughosta added the Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team label Jan 23, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 23, 2024
@Erikg346
Copy link

Hey @andrelrmarques, not sure why they did that but the workaround for me is adding synthetic-* pattern in Uptime setting indices pattern. This will allow you to use the Uptime rules and create separate alerts for synthetic monitors. Link to Discussion

@MatheusGelinskiPires
Copy link

Hey @andrelrmarques, not sure why they did that but the workaround for me is adding synthetic-* pattern in Uptime setting indices pattern. This will allow you to use the Uptime rules and create separate alerts for synthetic monitors. Link to Discussion

Hello @Erikg346 , it's a good workaround and I did the same here but the Uptime is being considered a legacy option by now so I am not sure how long it will works.

@jrentsch
Copy link

Just arrived here trying to do the same thing. Any resolution or movement on this?

@MatheusGelinskiPires
Copy link

Just arrived here trying to do the same thing. Any resolution or movement on this?

Nothing that I am aware of.

@smith smith added enhancement New value added to drive a business result Team:obs-ux-management Observability Management User Experience Team and removed Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team labels Jul 10, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

@shahzad31 shahzad31 self-assigned this Jul 12, 2024
@shahzad31 shahzad31 mentioned this issue Jul 12, 2024
Merged
@MakoWish
Copy link

MakoWish commented Aug 9, 2024

Also looking for a fix to this. Different monitors may require different criteria before sending out an alert, and the new Synthetics rules offer practically no customization nor filtering. You cannot deprecate and remove Uptime until Synthetics is a better solution. As of now, it is not.

shahzad31 added a commit to shahzad31/kibana that referenced this issue Oct 2, 2024
@shahzad31
[Synthetics] Improve synthetics alerting (elastic#186585)
b40857b 
## Summary

Fixes elastic#175298

Improve synthetics alerting !!

User will be able to create custom synthetics status alert by defining
three kind of criteria

### Monitor is down over last consective checks with threshold

<img width="639" alt="image"
src="https://github.com/elastic/kibana/assets/3505601/390da238-f7f2-4eb0-9606-3279b3199fdf">

### From Locations threshold

Will be considered down only when from defined number of locations

<img width="618" alt="image"
src="https://github.com/elastic/kibana/assets/3505601/24741a10-0880-4247-9048-8ce03df25bf5">

### Over time with checks threshold just like uptime custom status alert

<img width="631" alt="image"
src="https://github.com/elastic/kibana/assets/3505601/64e1c808-8d4b-4dd0-b794-eb7f4e5d1e6b">

---------

Co-authored-by: kibanamachine <[email protected]>
Co-authored-by: Dominique Clarke <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
Co-authored-by: Maryam Saeidi <[email protected]>
Co-authored-by: Justin Kambic <[email protected]>
(cherry picked from commit 82d0b00)

# Conflicts:
#	.github/CODEOWNERS
#	x-pack/plugins/observability_solution/synthetics/public/apps/synthetics/components/alerts/query_bar.tsx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shahzad31 shahzad31

Labels
enhancement New value added to drive a business result Team:obs-ux-management Observability Management User Experience Team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Synthetics] Improve synthetics alerting shahzad31/kibana
9 participants
@smith @jughosta @shahzad31 @jrentsch @elasticmachine @MatheusGelinskiPires @MakoWish @Erikg346 @andrelrmarques