Global alert management

1. A system comprising:

a first regional cloud exchange platform, associated with a first regional cloud exchange, that includes:

a first regional cloud services monitoring engine; and

a first regional cloud exchange monitoring engine;

a second regional cloud exchange platform, associated with a second regional cloud exchange, that includes:

a second regional cloud services monitoring engine; and

a second regional cloud exchange monitoring engine;

an alert triaging engine, coupled to the first regional cloud exchange platform and the second regional cloud exchange platform;

a root cause determination engine, coupled to the alert triaging engine;

a new alert definition engine, coupled to the root cause determination engine; and

a constraints mapping engine, coupled to the new alert definition engine;

wherein, in operation,

the alert triaging engine:

collects first related alerts associated with the first regional cloud exchange platform, including a first alert and a second alert, in an incoming alert queue;

determines the first alert is a known alert;

identifies a hierarchy of alerts with which the first alert is associated;

performs automated recovery in association with the first alert and the second alert;

verifies recovery associated with the first alert and the second alert; and

alerts a customer with a third alert associated with the first alert and the second alert;

the root cause determination engine:

analyzes the first alert and the second alert to identify an underlying cause of the first alert and the second alert;

the new alert definition engine:

defines a new alert type based on the identified underlying cause; and

the constraints mapping engine:

updates a constraints datastore with characteristics of the new alert type to update the hierarchy of alerts.

2. The system of claim 1 , wherein the alert triaging engine orchestrates resolution techniques associated with the first alert and the second alert.

3. The system of claim 1 , wherein the alert triaging engine follows a verification checklist associated with the first alert and the second alert.

4. The system of claim 1 , wherein the alert triaging engine acknowledges and closes a ticket associated with the first alert and the second alert.

5. The system of claim 1 , wherein the alert triaging engine prepares a report for review associated with the first alert and the second alert.

6. The system of claim 1 , wherein the alert triaging engine alerts an operations team with a fourth alert associated with the first alert and the second alert.

7. The system of claim 1 , wherein when traffic associated with a node of the first regional cloud exchange platform is interrupted, a customer is notified.

8. The system of claim 1 , wherein a call to a provider API is made to trigger a node restart.

9. The system of claim 1 , wherein if a region is down, provider availability on the region is verified and zone statuses from the provider are verified.

10. The system of claim 1 , wherein if a provider zone of the first regional cloud exchange platform is down, zone status from a provider is verified, cloud exchange platforms (CXPs) are reachable is verified, and nodes responsive on the provider zone are verified.

11. The system of claim 1 , wherein if a node of the first regional cloud exchange platform is down, node status from a provider is verified, infra controller node up is verified, tenant tunnel status is verified, tenant connector health status is verified to be healthy, and traffic flow status is verified.

12. The system of claim 1 , wherein, in operation, the alert triaging engine collects second related alerts associated with the second regional cloud exchange platform.

13. A method comprising:

collecting, by an alert triaging engine, first related alerts associated with a first regional cloud exchange platform, including a first alert and a second alert, in an incoming alert queue;

determining, by said alert triaging engine, the first alert is a known alert;

identifying, by said alert triaging engine, a hierarchy of alerts with which the first alert is associated;

performing, by said alert triaging engine, automated recovery in association with the first alert and the second alert;

verifying, by said alert triaging engine, recovery associated with the first alert and the second alert;

alerting, by said alert triaging engine, a customer with a third alert associated with the first alert and the second alert;

analyzing, by a root cause determination engine, the first alert and the second alert to identify an underlying cause of the first alert and the second alert;

defining, by said root cause determination engine, a new alert type based on the identified underlying cause;

updating, by the root cause determination engine, a constraints datastore with characteristics of the new alert type to update the hierarchy of alerts; wherein the alert triaging engine is coupled to a first regional cloud services exchange platform and a second regional cloud exchange platform, wherein each of the first and second regional cloud service exchange platforms includes a regional cloud services monitoring engine and a regional cloud exchange engine;

wherein the root cause determination engine is coupled to the alert triaging engine, and a new alert definition engine is coupled to the root cause determination engine; and

wherein a constraints mapping engine is coupled to the new alert definition engine.

14. The method of claim 13 , comprising:

orchestrating resolution techniques associated with the first alert and the second alert;

following a verification checklist associated with the first alert and the second alert;

acknowledging and closing a ticket associated with the first alert and the second alert;

preparing a report for review associated with the first alert and the second alert;

alerting an operations team with a fourth alert associated with the first alert and the second alert.

15. The method of claim 13 , wherein when traffic associated with a node of the first regional cloud exchange platform is interrupted, comprising:

notifying a customer;

making a call to a provider API to trigger a node restart.

16. The method of claim 13 , wherein if a region is down, comprising verifying provider availability on the region and zone statuses from the provider.

17. The method of claim 13 , wherein if a provider zone of the first regional cloud exchange platform is down, comprising verifying zone status from a provider, cloud exchange platforms (CXPs) are reachable, and nodes responsive on the provider zone.

18. The method of claim 13 , wherein if a node of the first regional cloud exchange platform is down, verifying node status from a provider, infra controller node up, tenant tunnel status, tenant connector health status is healthy, and traffic flow status.

19. The method of claim 13 , comprising collecting second related alerts associated with a second regional cloud exchange platform.