sysdig_monitor_alert_metric is missing grouping and scoping to team

[wosteven]

Hi,

when creating an Alert with "sysdig_monitor_alert_metric" resource (https://registry.terraform.io/providers/sysdiglabs/sysdig/latest/docs/resources/monitor_alert_metric) it is impossible to group the alert to a metric group and it is also impossible to create the alert in the scope of a team.

We heavily use teams, and we want to group alerts (like "ELK","KAFKA", ...). Alerts should only be visible to a specific team (or teams). The sysdig UI supports Metric Groups, when creating an Alert as a Member of a specific Team in UI it is also created in the scope of the team correctly.

ATM we create alerts with TF, then we need to manually copy the alerts to the target team (as they are exposed to default monitoing group only), and then we need to manually add the "group" in UI to each created alert.

You should consider changing "sysdig_monitor_alert_metric" resource to add a "group" attribute and a "team" attribute.

resource "sysdig_monitor_alert_metric" "elk_high_disk" {
    name = "ELK_PROD_DISK_FULL_WARNING"
    description = "The disk usage is very high."
    group = "ELK"  <<<< metric group
    team   = "TEAMID1"  <<<< metric is created in this teams scope
    severity = 2

    scope = "host.hostName starts with \"shared-${lower(var.stage)}-elk\" AND not fs.device contains \"/dev/loop\""
    metric = "max(avg(fs.used.percent)) > ${var.high_disk_threshold_percent}"
    ...
}

[tembleking]

I think you need instead to use the API token of the specific group.
The API tokens are different for every person in every team, that is, an API token identifies a single person in a single team.
When you switch teams, your API token changes as well.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

[github-actions]

This issue has been closed due to inactivity.