Terraform module to create monitor alerts resource on AZURE.
We eat, drink, sleep and most importantly love DevOps. We are working towards strategies for standardizing architecture while ensuring security for the infrastructure. We are strong believer of the philosophy Bigger problems are always solved by breaking them into smaller manageable problems. Resonating with microservices architecture, it is considered best-practice to run database, cluster, storage in smaller connected yet manageable pieces within the infrastructure.
This module is basically combination of Terraform open source and includes automatation tests and examples. It also helps to create and improve your infrastructure with minimalistic code instead of maintaining the whole infrastructure code yourself.
We have fifty plus terraform modules. A few of them are comepleted and are available for open source usage while a few others are in progress.
This module has a few dependencies:
- Terraform 1.x.x
- Go
- github.com/stretchr/testify/assert
- github.com/gruntwork-io/terratest/modules/terraform
IMPORTANT: Since the master
branch used in source
varies based on new modifications, we suggest that you use the release versions here.
Here are some examples of how you can use this module in your inventory structure:
module "monitor-alerts" {
source = "clouddrove/monitor-alerts/azure"
version = "1.0.0"
name = "app"
environment = "test"
label_order = ["name", "environment"]
actionGroups = {
"group1" = {
actionGroupName = "AlertEscalationGroup"
actionGroupShortName = "alertesc"
actionGroupRGName = module.resource_group.resource_group_name
actionGroupEnabled = "true"
actionGroupEmailReceiver = [
{
name = "example"
email_address = "example@gmail.com"
use_common_alert_schema = "true"
},
{
name = "test"
email_address = "test@gmail.com"
use_common_alert_schema = "true"
}
]
}
}
}
module "monitor-alerts" {
source = "clouddrove/monitor-alerts/azure"
version = "1.0.0"
name = "app"
environment = "test"
label_order = ["name", "environment"]
actionGroups = {
"group1" = {
actionGroupName = "AlertEscalationGroup"
actionGroupShortName = "alertesc"
actionGroupRGName = module.resource_group.resource_group_name
actionGroupEnabled = "true"
actionGroupEmailReceiver = [
{
name = "test"
email_address = "mahesh.yadav@clouddrove.com"
use_common_alert_schema = "true"
},
{
name = "test"
email_address = "test@gmail.com"
use_common_alert_schema = "true"
}
]
}
}
}
module "alerts" {
depends_on = [data.azurerm_monitor_action_group.example, ]
source = "clouddrove/monitor-alerts/azure"
name = "app"
environment = "test"
label_order = ["name", "environment"]
activity_log_alert = {
"test1" = {
alertname = "nsg-write"
alertrg = module.resource_group.resource_group_name
alertscopes = [module.resource_group.resource_group_id]
description = "Administrative alerts for nsg"
operation_name = "Microsoft.Network/networkSecurityGroups/write"
actionGroupID = data.azurerm_monitor_action_group.example.id
category = "Administrative"
}
}
}
Name | Description | Type | Default | Required |
---|---|---|---|---|
actionGroups | n/a | map(object({ |
{} |
no |
activity_log_alert | n/a | map(object({ |
{} |
no |
application | Application (e.g. cd or clouddrove ). |
string |
"" |
no |
environment | Environment (e.g. prod , dev , staging ). |
string |
"" |
no |
label_order | Label order, e.g. name ,application . |
list(any) |
[ |
no |
managedby | ManagedBy, eg 'CloudDrove' or 'AnmolNagpal'. | string |
"anmol@clouddrove.com" |
no |
metricAlerts | n/a | map(object({ |
{} |
no |
name | Name (e.g. app or cluster ). |
string |
"" |
no |
repository | Terraform current module repo | string |
"" |
no |
tags | Additional tags (e.g. map(BusinessUnit ,XYZ ). |
map(any) |
{} |
no |
Name | Description |
---|---|
ag | n/a |
metric-alerts | n/a |
In this module testing is performed with terratest and it creates a small piece of infrastructure, matches the output like ARN, ID and Tags name etc and destroy infrastructure in your AWS account. This testing is written in GO, so you need a GO environment in your system.
You need to run the following command in the testing folder:
go test -run Test
If you come accross a bug or have any feedback, please log it in our issue tracker, or feel free to drop us an email at hello@clouddrove.com.
If you have found it worth your time, go ahead and give us a ★ on our GitHub!
At CloudDrove, we offer expert guidance, implementation support and services to help organisations accelerate their journey to the cloud. Our services include docker and container orchestration, cloud migration and adoption, infrastructure automation, application modernisation and remediation, and performance engineering.
We are The Cloud Experts!
We ❤️ Open Source and you can check out our other modules to get help with your new Cloud ideas.