Add VPN monitoring alerts to 2-networking and VPN usage chart #1412
Conversation
This file contains 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
ludoo
approved these changes
Jun 2, 2023
|
@afda16 We have a check to ensure the peering and VPN stages are identical except for a few resources. To make the tests pass you'll have to replicate the same change in the peering stage. In fact, I think it makes sense to have this in all networking stages with VPNs. |
afda16
force-pushed
the
afda16/vpn-alerts
branch
3 times, most recently
from
d0a862f to
9e32a86
Compare
|
Thanks @juliocc , I'll add it to the rest of networking stages |
afda16
changed the title
afda16
force-pushed
the
afda16/vpn-alerts
branch
2 times, most recently
from
c03c58d to
b34b989
Compare
afda16
changed the title
afda16
force-pushed
the
afda16/vpn-alerts
branch
6 times, most recently
from
6fb2e6c to
e71ab7b
Compare
aurelienlegrand
approved these changes
Jun 5, 2023
afda16
changed the title
The Fast stage 2-networking-* currently adds a monitoring dashboard for VPN metrics. This change adds an additional chart to monitor the usage of the VPN bandwidth. This change also adds the following monitoring alerts: * VPN tunnel established * [VPN bandwidth](https://cloud.google.com/network-connectivity/docs/vpn/how-to/viewing-logs-metrics#define-bandwidth-alerts) To configure the alerts, there is a new `alert_config` variable with defined default values. The alerts are created in the stage `b` by default. In the stages a, c, d, and e, the alerts are created if the user creates the On-prem VPN. To disable the creation of alerts, add the following to `terraform.tfvars`: ``` alert_config = { vpn_tunnel_established = null vpn_tunnel_bandwidth = null } ```
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.
The Fast stage 2-networking-* currently adds a monitoring dashboard for VPN metrics. This change adds an additional chart to monitor the usage of the VPN bandwidth.
This change also adds the following monitoring alerts:
To configure the alerts, there is a new
alert_configvariable with defined default values.The alerts are created in the stage
bby default. In the stages a, c, d, and e, the alerts are created if the user creates the On-prem VPN.To disable the creation of alerts, add the following to
terraform.tfvars: