Other Types of Thresholds

In addition to autothresholds, which are automatically calculated, there are a few other types of thresholds that can be used either for manual metrics or autometrics. To set these other types of thresholds, navigate to the relevant metric and click the Edit Metric button to surface the Edit Metric modal.

No threshold

This indicates that the metric will never send a notification. This setting can be useful for tracking debugging-level information that won't detect an issue on its own, but may be useful when another metric on the same table is alerting.

Constant thresholds

Constant thresholds are useful if there is a specific business logic that can be asserted about the values in the column. For example, if you know that a number stored in the database should be a percentage, the numeric value would need to be between 0 and 100 at all times.

The metric will alert if the value computed is outside of the specified bounds. Either of the bounds can be specified, or both.

Relative thresholds

Relative thresholds are designed for doing comparisons to previous values, such as week over week comparisons. The days to look back setting determines how far back to compare the current values. The alert if up/down % input box allows you to tell Bigeye how much of a percent deviation is acceptable.

Freshness schedule thresholds

Freshness schedule thresholds are designed for infrequently-updated tables that should be loaded on a schedule.

The update schedule determines when the lowest point of the check should be, specified in Cron Formatting.

The timezone is specified either as full name (America/Los Angeles), hour offset (-0800), or abbreviation (PST).

Delay at update is the minimum value that the check will have, specified in hours.

The threshold will increase from that point until the next execution of the cron schedule.

Example: