[BUG] Expected value for non-anomalous value

[kaituo]

What is the bug?
From a customer inquiry: why does AOS refer to non-anomalous spikes in error counts (such as shown here) as expected values? In fact, they are actual values, and the reference to them being expected values is causing some confusion with the customer, who thinks of an expected value as something that is calculated like a moving average. Can we say they are "expected" in the sense they are non-anomalous?

How can one reproduce the bug?

What is the expected behavior?
Backend has expected value for anomalous values, not for non-anomalous values. For non-anomalous values, expected value = actual value. This is confusing to cx from moving average and statistics background. I'd suggest we change to only show expected value when there is an anomaly.

What is your host/environment?

• OS: [e.g. iOS]
• Version [e.g. 22]
• Plugins

Do you have any screenshots?

Do you have any additional context?
Add any other context about the problem.