Conversation
RobbeBultynck
suggested changes
Mar 10, 2026
Contributor
RobbeBultynck
left a comment
RobbeBultynck
left a comment
There was a problem hiding this comment.
It's a good description, but I would preferer 2 extra things:
- A reason why to use it.
- A note to warn the user this is not made for normal operations.
A reason why to use it:
We've noticed that for some extreme scenarios the connection could drop due to a huge amount of alarm events flooding the connection.
By using "EnableAlarmSubscriptions=false" the user is able to use DataMiner Cube without subscribing on any alarm events.
This should result in a working DataMiner Cube (in a degraded state) just to be able to reconfigure the alarming.
RobbeBultynck
approved these changes
Mar 10, 2026
MariekeGO
approved these changes
Mar 10, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
@RobbeBultynck, could you please review this pull request to confirm the accurate inclusion of release note 44779 in the documentation? Thanks in advance!