[GDB-13346] Enhance CloudWatch monitoring: add new alarms and refactor existing ones #129
+174
−73
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
simonzhekoff
force-pushed
the
GDB-13346
branch
2 times, most recently
from
140fa3a to
6719d12
Compare
…nt, and root ebs volume disk_used_percent, Optimized alarms
simonzhekoff
force-pushed
the
GDB-13346
branch
from
6719d12 to
2dcce29
Compare
simonzhekoff
changed the title
| threshold = "0" | ||
| alarm_actions = [aws_sns_topic.graphdb_sns_topic.arn] | ||
| ok_actions = [aws_sns_topic.graphdb_sns_topic.arn] | ||
| treat_missing_data = "notBreaching" |
Contributor
There was a problem hiding this comment.
why notBreaching ? if the agent is not sending data, for example because the VM has exhausted the available memory then it should trigger an alert.
| ImageId = data.aws_instance.by_id[each.key].ami | ||
| InstanceType = data.aws_instance.by_id[each.key].instance_type | ||
| path = "/" | ||
| device = "nvme0n1p1" |
Contributor
There was a problem hiding this comment.
is the device always going to be nvme0n1p1 ?
Contributor
Author
There was a problem hiding this comment.
For the nitro-based instances, yes, I will check for an automated way so it can find the right device automatically.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR enhances the CloudWatch monitoring configuration and improves alarm coverage and consistency across all GraphDB nodes.
Key Changes
Refactored existing alarms:
• Added treat_missing_data = "notBreaching" to prevent false positives during deployment or downtime.
• Unified comparison_operator to GreaterThanOrEqualToThreshold for consistency.
• Introduced new per-node alarms
• disk_used_percent — triggers when root disk usage exceeds the threshold.
• mem_used_percent — monitors memory utilization per instance.
• cpu_utilization — tracks CPU usage individually for each node.
• Updated CloudWatch Agent configuration
• Added InstanceId as an appended dimension to support per-node metric granularity and accurate alarm mapping.
Related Issues
[GDB-13446]
Changes
Checklist