Check: alerts | ComputeSphere Learn

Goal: Confirm you can choose what to alert on, set a rule that won't flap, and route notifications to a webhook.

Four questions: three on Module 6, one on Module 4. Every answer explains itself, right or wrong.

Your team gets a CPU alert most afternoons. Each time, someone looks, the service is answering quickly, and nobody does anything. What's the best change?Mute the alert notifications in chatRaise the threshold or evaluation period, or alert on a symptom insteadRaise its severity so people take it seriously

You create a Memory rule, threshold 90, evaluation period 300, for the lab environment, but never turn on the project's Alerts switch. Memory sits at 95% for ten minutes. Who hears about it?NobodyEveryone on the accountWhoever deployed the service

You're about to delete the service a webhook endpoint in your notification settings points at. What do you do first?Remove the endpoint from Notifications and saveDelete the project's alert rulesNothing: the endpoint goes with the service

From Module 4: an app takes 90 seconds to start. Its health check has Initial delay 5 and Check interval 10, and it answers 503 until it's ready. What happens during a deploy?Users get 503s for 90 secondsIt stays out of traffic until it's ready, then goes liveIt's restarted before it finishes starting

Retry as often as you like.