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

Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/observability/synthetics/custom_status_rule·ts - Observability Rules Synthetics SyntheticsCustomStatusRule TimeWindow - Location threshold = 1 - grouped by location - 1 down location should trigger recovered alert #196257

Open
kibanamachine opened this issue Oct 15, 2024 · 7 comments
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:obs-ux-management Observability Management User Experience Team v9.0.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Oct 15, 2024

A test failed on a tracked branch

Error: expected { status: 'active',
  reason: 'Monitor "Monitor time based at 8:47 AM" from Dev Service is down. Alert when 5 checks are down within the last 5 minutes from at least 1 location.',
  locationNames: 'Dev Service',
  locationId: 'dev',
  linkMessage: '- Link: https://localhost:5601/app/synthetics/monitor/4ef166b7-c2c1-408e-9975-0de0984e3aed/errors/Test%20private%20location-18524a3d9a7-0?locationId=dev',
  'monitor.id': '4ef166b7-c2c1-408e-9975-0de0984e3aed' } to have a property 'reason' of 'Monitor "Monitor time based at 8:47 AM" from Dev Service is recovered. Alert when 5 checks are down within the last 5 minutes from at least 1 location.', but got 'Monitor "Monitor time based at 8:47 AM" from Dev Service is down. Alert when 5 checks are down within the last 5 minutes from at least 1 location.'
    at Assertion.assert (expect.js:100:11)
    at Assertion.property (expect.js:417:10)
    at Context.<anonymous> (custom_status_rule.ts:804:55)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-on-merge - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 15, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 15, 2024
@kibanamachine kibanamachine added the Team:obs-ux-management Observability Management User Experience Team label Oct 15, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 15, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

Skipped

main: 72d3eab

SoniaSanzV pushed a commit to SoniaSanzV/kibana that referenced this issue Dec 9, 2024
SoniaSanzV pushed a commit to SoniaSanzV/kibana that referenced this issue Dec 9, 2024
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 9, 2024
Samiul-TheSoccerFan pushed a commit to Samiul-TheSoccerFan/kibana that referenced this issue Dec 10, 2024
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:obs-ux-management Observability Management User Experience Team v9.0.0
Projects
None yet
Development

No branches or pull requests

2 participants