Base rules and framework-specific rules

Asserts uses a curated library of rules to analyze incoming time-series data and generate important insights called assertions. These assertions are then classified into a model called SAAFE, which stands for Saturation, Amend, Anomaly, Failure, and Error. The implementation of Asserts involves two sets of rules: base rules and framework-specific rules, which are responsible for raising these assertions.

Base rules are for common request and resource metrics across platforms and frameworks. The table below summarizes base assertions raised by base rules.

	Assertion	SAAFE Category
Request	RequestRateAnomaly	Anomaly
	LatencyAverageAnomaly	Anomaly
	LatencyAverageBreach	Error
	LatencyP99ErrorBuildup	Error
	ErrorRatioAnomaly	Anomaly
	InboundClientErrorAnomaly	Anomaly
	ErrorRatioBreach	Error
	ErrorBuildup	Error
Logging	LoggerRateAnomaly	Anomaly
	ErrorLogRateBreach	Error
Resource	Saturation	Saturation
	ResourceRateAnomaly	Anomaly
	ResourceRateBreach	Error
	ResourceMayExhaust	Error

Framework-specific rules raise a variety of assertions, typically falling into the categories of Failure, Amend, and Saturation. For more information about the SAAFE model, refer to Understanding the SAAFE Model.

The following image shows a sample of frameworks and libraries for which built-in assertions are available.