Severity of dropped modulation events

[NonCertus]

Question: Should dropped modulation events (to a critical level only) be upgraded to severity “critical” in every case?
(modulation level: critical -> event: critical)

[itsDNNS]

The event severity shown here is derived from the resulting modulation level after the drop, not only from the fact that a modulation drop occurred.

In the first example, the channel dropped from 64QAM to QPSK. QPSK is a very low modulation level and indicates a severe degradation of signal quality, so the event is classified as critical.

In the second example, the channel dropped from 64QAM to 16QAM. This is still a degradation, but the resulting modulation level is not as severe as QPSK, so the event is classified as warning.

So the intended logic is roughly:

drop to QPSK = critical

drop to 16QAM = warning

This means the severity reflects how bad the resulting modulation state is, not just that a drop happened.

[NonCertus]

I just thought that a drop to 16QAM should maybe also be considered "critical" for consistency, because an SC-QAM upstream modulation of 16QAM and below is considered "low/red" in "Modulation Performance". So reaching 16QAM is already quite bad. However, it’s also reasonable to consider a drop to 16QAM as not severe enough to qualify as a "critical" event.

[itsDNNS]

The original idea behind the event severity was slightly different from the "Modulation Performance" view.

For modulation performance, the goal is to show the technical quality of the current modulation state. From that perspective, 16QAM and below being shown as low/red makes sense, because it is already a poor upstream modulation level.

For modulation drop events, my initial thinking was more focused on the practical impact compared to the expected or contractually agreed upstream performance. At least in Germany, a drop to 16QAM can often still be enough to reach the contracted upload speed, while a drop to QPSK is much more likely to indicate a serious service impact. That is why I originally treated QPSK as "critical", while 16QAM was still classified as "warning".

So I still see "Modulation Performance" and "Modulation Drop Events" as related, but not necessarily identical severity models:

"Modulation Performance" = How good or bad is the current modulation level technically?

"Modulation Drop Event" = How severe is the degradation likely to be from a user impact perspective?

That said, I also understand the consistency argument. If 16QAM is already considered low/red in modulation performance, it may be confusing for users if a drop to 16QAM is only shown as "warning" in the event timeline.