NationTech/harmony
5
0
Fork 2
Code Issues 40 Pull Requests 14 Actions Packages Projects Releases 1 Wiki Activity

monitoring-alerting #30

Merged
wjro merged 12 commits from monitoring-alerting into master 2025-05-06 17:50:57 +00:00
Conversation 1 Commits 12 Files Changed 6 +306
wjro commented 2025-05-05 16:50:30 +00:00
Owner
Copy Link
No description provided.
wjro added 4 commits 2025-05-05 16:50:31 +00:00
WIP: initial layout for MonitoringStackScore 40cd765019
wip: initial layout 6c145f1100
wip: alerting a6bcaade46
feat: added Score and topology to create kube prometheus monitoring and alerting stack 2f8e150f41
wjro added 1 commit 2025-05-05 17:40:40 +00:00
added file fbd466a85c
wjro added 1 commit 2025-05-05 19:38:42 +00:00
feat: added basic alert for pvc 95% full to kube-prometheus score e7cfbf914a
wjro added 1 commit 2025-05-05 20:37:23 +00:00
fix: refactor so that the topology installs the MonitoringAlertingStack depending on if it is already present in the cluster 88270ece61
taha reviewed 2025-05-06 14:17:17 +00:00
harmony/src/modules/monitoring/monitoring_alerting.rs Outdated
@@ -0,0 +16,4 @@
#[derive(Debug)]
pub struct MonitoringAlertingStackScore {
pub monitoring_stack: Vec<Box<dyn Score<MonitoringAlertingTopology>>>,
taha commented 2025-05-06 14:17:17 +00:00
Collaborator
Copy Link

Why does the MonitoringAlertingStackScore need a Vec<Box<dyn Score<MonitoringAlertingTopology>>>? It seems like it's never used for anything.

A score's variables should be what is needed to set it up, i.e. any values, rules, etc you want to pass in for the interpret to use to spin up the score

Why does the `MonitoringAlertingStackScore` need a `Vec<Box<dyn Score<MonitoringAlertingTopology>>>`? It seems like it's never used for anything. A score's variables should be what is needed to set it up, i.e. any values, rules, etc you want to pass in for the interpret to use to spin up the score
wjro added 3 commits 2025-05-06 15:54:33 +00:00
fix: correctly pass namespace and monitoring stack to topology so it can be used to init the maestro and exec the score 472a3c1051
Merge remote-tracking branch 'origin/master' into monitoring-alerting cd8542258c
wip: trying to get the kube-prometheus score to install 2d74c66fc6
wjro added 1 commit 2025-05-06 16:23:18 +00:00
fix:installs helm chart d9921b857b
wjro added 1 commit 2025-05-06 17:43:05 +00:00
fix:yaml structure ef9c1cce77
wjro merged commit 4a9b95acad into master 2025-05-06 17:50:57 +00:00
johnride deleted branch monitoring-alerting 2025-05-06 17:55:41 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Architecture Decision Record
Good first issue
RFC
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
johnride jvtrudel letian stremblay wjro
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: NationTech/harmony#30
No description provided.
Delete Branch "monitoring-alerting"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?