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: Serverless Observability API Integration Tests.x-pack/test_serverless/api_integration/test_suites/observability/burn_rate_rule/burn_rate_rule·ts - Serverless observability API Burn rate rule Rule creation should set correct information in the alert document #187525

Closed
kibanamachine opened this issue Jul 3, 2024 · 3 comments
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:obs-ux-management Observability Management User Experience Team

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: expected { 'kibana.alert.reason': 'SUPPRESSED - HIGH: The burn rate for the past 6h is 1000 and for the past 30m is 1000. Alert when above 1.4 for both windows',
  'kibana.alert.evaluation.threshold': 1.4,
  'kibana.alert.evaluation.value': 999.9999999999991,
  'slo.id': 'my-custom-id',
  'slo.revision': 1,
  'slo.instanceId': '*',
  'kibana.alert.rule.category': 'SLO burn rate',
  'kibana.alert.rule.consumer': 'observability',
  'kibana.alert.rule.execution.uuid': 'c117c60c-a81c-4f9c-9e62-74c03a41a8f6',
  'kibana.alert.rule.name': 'SLO Burn Rate rule',
  'kibana.alert.rule.parameters': 
   { sloId: 'my-custom-id',
     dependencies: [ [Object] ],
     windows: [ [Object], [Object], [Object], [Object] ] },
  'kibana.alert.rule.producer': 'observability',
  'kibana.alert.rule.revision': 0,
  'kibana.alert.rule.rule_type_id': 'slo.rules.burnRate',
  'kibana.alert.rule.tags': [ 'observability' ],
  'kibana.alert.rule.uuid': '929122d1-3771-4938-9d1c-9f449ba03ab7',
  'kibana.space_ids': [ 'default' ],
  '@timestamp': '2024-07-03T21:43:32.414Z',
  'event.action': 'open',
  'event.kind': 'signal',
  'kibana.alert.rule.execution.timestamp': '2024-07-03T21:43:32.414Z',
  'kibana.alert.action_group': 'slo.burnRate.suppressed',
  'kibana.alert.flapping': false,
  'kibana.alert.flapping_history': [ true ],
  'kibana.alert.instance.id': '*',
  'kibana.alert.maintenance_window_ids': [],
  'kibana.alert.consecutive_matches': 1,
  'kibana.alert.status': 'active',
  'kibana.alert.uuid': 'b0d782b9-de9c-4815-9755-b23336756c36',
  'kibana.alert.severity_improving': false,
  'kibana.alert.workflow_status': 'open',
  'kibana.alert.duration.us': 0,
  'kibana.alert.start': '2024-07-03T21:43:32.414Z',
  'kibana.alert.time_range': { gte: '2024-07-03T21:43:32.414Z' },
  'kibana.version': '8.15.0-SNAPSHOT',
  tags: [ 'observability' ] } to have a property 'kibana.alert.reason' of 'SUPPRESSED - CRITICAL: The burn rate for the past 1h is 1000 and for the past 5m is 1000. Alert when above 3.36 for both windows', but got 'SUPPRESSED - HIGH: The burn rate for the past 6h is 1000 and for the past 30m is 1000. Alert when above 1.4 for both windows'
    at Assertion.assert (expect.js:100:11)
    at Assertion.property (expect.js:417:10)
    at Context.<anonymous> (burn_rate_rule.ts:295:43)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:73:16)

First failure: kibana-on-merge - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jul 3, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 3, 2024
@kibanamachine kibanamachine added the Team:obs-ux-management Observability Management User Experience Team label Jul 3, 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 Jul 3, 2024
@mgiota
Copy link
Contributor

mgiota commented Jan 7, 2025

This looks like an old ticket. Shall we close this?

@mgiota mgiota self-assigned this Jan 7, 2025
@mgiota
Copy link
Contributor

mgiota commented Jan 7, 2025

Closing this one. SLO burn rate rule tests have been migrated to the SLO deployment agnostic solution

@mgiota mgiota closed this as completed Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:obs-ux-management Observability Management User Experience Team
Projects
None yet
Development

No branches or pull requests

3 participants