Feature/Address Alarm Correlation and Aggregation Discussions #17 #18 #554
Conversation
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
…ation and Aggregation Project in addition to adding the data source and alarm types header in alarm filters area
mohamedawnallah
force-pushed
the
feature/address-discussions-#17-#18
branch
from
ff13cd1 to
c2c88fd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
This pull request addresses the fixes required for alarm correlation and aggregation discussions 17, 18, and adding the data source and alarm types header in the alarm filters area so that it could differentiate between the data source and alarm type
How Has This Been Tested?
All tests passed:
npm testScreenshots (if appropriate):
Types of changes
Checklist: