Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

elastic / kibana Public

Notifications You must be signed in to change notification settings
Fork 8.3k
Star 20.3k

Code
Issues 5k+
Pull requests 1.3k
Discussions
Actions
Projects 3
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

[Security Solution] [DETECTIONS] Set rule status to failure only on large gaps#71549

Merged

dhurley14 merged 6 commits intoelastic:masterelastic/kibana:masterfrom dhurley14:gap-detection-ui-warningdhurley14/kibana:gap-detection-ui-warningCopy head branch name to clipboard

Jul 14, 2020

+258-84

Conversation Commits6 (6)Checks Files changed

Commits

Commits on Jul 13, 2020

only display gap error when a gap is too large for the gap mitigation code to cover, general code cleanup, adds some tests for separate function
dhurley14
committed
removes throwing of errors and log error and return null for maxCatchup, ratio, and gapDiffInUnits properties
dhurley14
committed
forgot to delete commented out code
dhurley14
committed
remove math.abs since we fixed this bug by switching around logic when calculating gapDiffInUnits in getGapMaxCatchupRatio fn
dhurley14
committed

Commits on Jul 14, 2020

updates tests for when a gap error should be written to rule status
dhurley14
committed
fix typo
dhurley14
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.