34 alerts

[kislerdm]

Why do we need it

To ensure reliability

What changed

• Added the dashboard with critical metrics for the app server
• Added the metric, see #34
• Added integration to slack to get notification on alerts/aws cloudwatch alarms
• Added CI pipeline to automate monitoring setting

Closes #34

[github-actions[bot]]

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Validation Output

``` Success! The configuration is valid.  ```

Terraform Plan 📖success

Show Plan

``` aws_cloudwatch_dashboard.main: Refreshing state... [id=core] aws_sns_topic.this: Refreshing state... [id=arn:aws:sns:us-east-2:027889758114:core-monitoring] aws_cloudwatch_metric_alarm.request_error_rate: Refreshing state... [id=core-response-error-rate] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place Terraform will perform the following actions: # aws_sns_topic.this will be updated in-place ~ resource "aws_sns_topic" "this" { id = "arn:aws:sns:us-east-2:027889758114:core-monitoring" name = "core-monitoring" ~ policy = jsonencode( ~ { - Version = "2008-10-17" -> null # (1 unchanged element hidden) } ) tags = {} # (10 unchanged attributes hidden) } Plan: 0 to add, 1 to change, 0 to destroy. ───────────────────────────────────────────────────────────────────────────── Saved the plan to: /tmp/terraform.tfplan To perform exactly these actions, run the following command to apply: terraform apply "/tmp/terraform.tfplan" ```

Pusher: @kislerdm, Action: pull_request, Workflow: TF:Monitoring

[kislerdm]

@deim thanks for the feedback!