-
Notifications
You must be signed in to change notification settings - Fork 26
MTM-62614 add release notes about raising Messaging Service alarms on common errors #3861
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tjegorow-c8y
wants to merge
4
commits into
develop
Choose a base branch
from
feature/MTM-62614/raise-messaging-service-alarms-on-error
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
508ae00
MTM-62614 add release notes about raising Messaging Service alarms on…
tjegorow-c8y fdc642f
Update content/change-logs/platform-services/cumulocity-2025-332-0-ra…
BeateRixen f4eafc0
MTM-62614 apply suggestions from review
tjegorow-c8y 16dba92
Update content/change-logs/platform-services/cumulocity-2025-332-0-ra…
BeateRixen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
17 changes: 17 additions & 0 deletions
17
...tform-services/cumulocity-2025-332-0-raise-messaging-service-alarms-on-error.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| --- | ||
| date: 2025-10-03 | ||
| title: "Raising Messaging Service alarms on common errors" | ||
tjegorow-c8y marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| product_area: Platform services | ||
| change_type: | ||
| - value: change-QHu1GdukP | ||
| label: Feature | ||
tjegorow-c8y marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| component: | ||
| - value: component-2Yri1-l3n | ||
| label: Messaging Service | ||
| build_artifact: | ||
| - value: tc-QHwMfWtBk7 | ||
| label: cumulocity | ||
| ticket: MTM-62614 | ||
| version: 2025.332.0 | ||
| --- | ||
| With this change, the {{< product-c8y-iot >}} platform raises a Messaging Service alarm when messages fail to be processed (for example, by the Notification 2.0 feature) due to common issues. These issues initially are about reaching backlog quota or topic limit, so issues were the customer should take the action to resolve it. | ||
tjegorow-c8y marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.