When an incident occurs, there is a key question:<\/p>\n\n
\ud83d\udc49 what if no one responds?<\/strong><\/em><\/p>\n\n That’s where automatic scaling comes in.<\/p>\n\n But although they sound complex, they actually work on a fairly simple logic.<\/p>\n\n An automatic scaling is:<\/p>\n\n a process that moves an alert to another person or level if there is no response in a certain amount of time<\/p>\n\n It is like saying:<\/p>\n\n “if no one takes this… the system makes sure someone else does.”<\/p>\n\n Because without scaling:<\/p>\n\n And often the problem is not technical.<\/p>\n\n It is human:<\/p>\n\n \ud83d\udc49 scaling eliminates that uncertainty.<\/p>\n\n Let’s look at it simply:<\/p>\n\n It can come from:<\/p>\n\n \ud83d\udc49 something is not working right<\/p>\n\n The system sends the alert to:<\/p>\n\n \ud83d\udc49 the person who is on duty or assigned.<\/p>\n\n A key condition comes into play here:<\/p>\n\n \ud83d\udc49 waiting time (e.g.: 5 minutes)<\/p>\n\n The system automatically:<\/p>\n\n If no one responds:<\/p>\n\n \ud83d\udc49 climbs again<\/p>\n\n Until:<\/p>\n\n \ud83d\udc49 someone confirms that he took the incident.<\/p>\n\n Scenario<\/strong><\/p>\n\n If you answer<\/strong><\/p>\n\n \ud83d\udc49 escalation is stopped<\/p>\n\n If you do not respond<\/strong><\/p>\n\n \ud83d\udc49 N2 is notified.<\/p>\n\n If N2 also does not respond<\/strong><\/p>\n\n \ud83d\udc49 can be upgraded to N3 or to a larger group<\/p>\n\n all this happens automatically<\/p>\n\n The most common.<\/p>\n\n \ud83d\udc49 “if you don’t respond in X minutes, I’ll escalate.”<\/p>\n\n Depending on the impact:<\/p>\n\n Based on levels:<\/p>\n\n In some cases:<\/p>\n\n \ud83d\udc49 several people are notified at the same time<\/p>\n\n Good scaling:<\/p>\n\n \ud83d\udc49 it’s not just about scaling… it’s about scaling judiciously.<\/p>\n\n Because it eliminates something critical:<\/p>\n\n the dependence on someone “remembering<\/p>\n\n The system:<\/p>\n\n \ud83d\udc49 simply run<\/p>\n\n With well-defined scaling:<\/p>\n\n Automatic scaling is not just another feature.<\/p>\n\n They are one of the key pieces to ensure that incidents do not remain in the air.<\/p>\n\n Because in operation:<\/p>\n\n the most dangerous thing is not the alert…<\/p>\n\n \ud83d\udc49 is that no one takes it<\/p>\n\n If you’re relying on people to remember to scale or follow up today, you’re probably leaving room for error.<\/p>\n\n 24Cevent allows you to define automatic escalation rules, ensuring that each alert moves forward until someone takes it, with configurable timing, clear accountabilities and effective notification at every stage.<\/strong><\/p>\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" When an incident occurs, there is a key question: \ud83d\udc49 what if no one responds? That’s where automatic scaling comes in. But although they sound complex, they actually work on a fairly simple logic. In simple An automatic scaling is: a process that moves an alert to another person or level if there is no […]<\/p>\n","protected":false},"author":2,"featured_media":5116,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[178],"tags":[328,330,329,331,332],"class_list":["post-5192","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-knowledge-center","tag-automatic-scaling","tag-escalate-it-alerts","tag-escalations","tag-scaling-levels","tag-types-of-scaling"],"_links":{"self":[{"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/posts\/5192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/comments?post=5192"}],"version-history":[{"count":3,"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/posts\/5192\/revisions"}],"predecessor-version":[{"id":5207,"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/posts\/5192\/revisions\/5207"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/media\/5116"}],"wp:attachment":[{"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/media?parent=5192"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/categories?post=5192"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/24cevent.com\/en\/wp-json\/wp\/v2\/tags?post=5192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}In simple<\/h1>\n\n
Why are they important?<\/h1>\n\n
\n
\n
How does it work step by step?<\/h1>\n\n
1. An alert is generated<\/h2>\n\n
\n
2. The first responsible party (N1) is notified.<\/h2>\n\n
3. A response is expected<\/h2>\n\n
4. If no response \u2192 scale<\/h2>\n\n
\n
5. The process continues<\/h2>\n\n
Simple example<\/h1>\n\n
\n
Types of scaling<\/h1>\n\n
Time-based scaling<\/h2>\n\n
Scaling by criticality<\/h2>\n\n
\n
Hierarchical escalation<\/h2>\n\n
\n
Parallel scaling<\/h2>\n\n
Common errors<\/h1>\n\n
\u274c Climbing too fast<\/h2>\n\n
\n
\u274c Climbing too late<\/h2>\n\n
\n
\u274c Scaling without context<\/h2>\n\n
\n
\u274c Do not confirm<\/h2>\n\n
\n
What makes it work well?<\/h1>\n\n
\n
Why does the operation change so much?<\/h1>\n\n
\n
So, what do you achieve?<\/h1>\n\n
\n
<\/h1>\n\n
<\/h1>\n\n