MTM-62614 add release notes about raising Messaging Service alarms on common errors

[tjegorow-c8y]

No description provided.

[github-actions]

Preview available here

[BeateRixen]

Please leave the date empty as it will be filled in automatically. Even if the change has already been deployed on eu-latest some time ago, it is not recommended to use an older date here, as people might not see the change log if they only check for the latest changes per date.

[scmi-c8y]

All good with me, but see @BeateRixen's comment about the date.

[JanePorter]

I cannot find any information in the Jira ticket on precisely when the alarm will be raised, how the customer knows what caused the alarm or any other information. The current change log entry does not provide any information on this either.

[scmi-c8y]

I cannot find any information in the Jira ticket on precisely when the alarm will be raised, how the customer knows what caused the alarm or any other information. The current change log entry does not provide any information on this either.

What do you think, @tjegorow-c8y? We deliberately left this a bit vague so we can change the set of things that trigger the alarms in future. I think it currently only applied to backlog quotas so we could rewrite it to be explicitly about that and link to the user doc that explains how the quotas work and how to avoid overflows?

[BeateRixen]

@tjegorow-c8y @scmi-c8y What is the status of this PR? Since it is a change log, it should be deployed close to the related software build, not sure if this is already on eu-latest?