The first choice, checked by default, is the verified email address of the account you’re using when you create the policy. To create a policy, you must select at least one of the two possible notification methods: email or Slack. To ensure that worker node alert policies persist on node recycling, use tags, for example the cluster name, instead of worker node names. Kubernetes worker nodes do not retain their names when a node is recycled. Adding tags to an alert policy provides flexibility in deciding which Droplets are covered by the policy by adding or removing tags from Droplets. The Select Droplets or Tags section includes a field where you apply the alert policy to specific Droplets or groups of Droplets.Īdding Droplets by name allows you to target individual resources unambiguously. Pick the alert interval, which is how long a Droplet must exceed the threshold before a notification is triggered:.In most scenarios, alerting when usage climbs above the threshold is the more helpful option because high usage tells us that the current resources may no longer be sufficient An appropriate value here will depend on the metric, the goal of the alert, and the typical server usage patterns. Specify the usage threshold itself as either a percentage of the total available capacity being used, or as a usage rate depending on the selected metric.Disk Utilization: The percentage of the root disk storage being used, out of 100%.Memory Utilization: The percentage of total memory being used, out of 100%.Disk - Write: The write activity for the Droplet’s disks, in MB/s.Disk - Read: The read activity for the Droplet’s disks, in MB/s.Bandwidth - Outbound: The amount of outgoing traffic from the Droplet, in MBps.Bandwidth - Inbound: The amount of incoming traffic to the Droplet, in MBps.CPU: The percentage of total CPU used on the Droplet, out of 100%.The pattern for defining an alert policy is the same for all metrics: In the control panel, click the Create button in the top menu and select Alert Policies: Once the metrics agent is running, you can begin creating alert policies. Kubernetes worker nodes, a kind of Droplet, already have the metrics agent by default.
#Digitalocean monit install#
Like other DigitalOcean Monitoring functionalities, the alert policies and notifications feature relies on information provided by the DigitalOcean metrics agent: a lightweight, open-source program that gathers metrics.īefore setting up alert policies, you must install the metrics agent on each of the participating Droplets.
It provides additional Droplet graphs and supports configurable metrics alert policies with integrated email Slack notifications to help you track the operational health of your infrastructure.
DigitalOcean Monitoring is a free, opt-in service that gathers metrics about Droplet-level resource utilization.
0 kommentar(er)
