Associating capabilities and alarms
Techniques are described for monitoring the health of services in a computing environment such as a data center. More particularly, the present disclosure describes techniques for monitoring the health and availability of capabilities in a computing environment such as a data center by enabling alarms to be associated with the capabilities. A capability refers to a set of resources in a data center. By providing the ability to associate an alarm with a capability, the health or availability of the associated capability can be monitored or ascertained by tracking the state of the alarm associated with the capability. For example, if the alarm associated with a particular capability is triggered, it may indicate that the particular capability and the one or more resources corresponding to the particular capability are not in a healthy state. Accordingly, by monitoring alarms associated with capabilities, the health of the associated capabilities can be ascertained.
1. A computer-implemented method comprising:
identifying an association between an alarm and a first capability, wherein the first capability corresponds to a functionality associated with a first service;
monitoring the alarm;
determining that the alarm is in a triggered state based on the monitoring;
responsive to determining that the alarm is in a triggered state, changing a state of the first capability from a healthy state to an unhealthy state; and
responsive to changing the state of the first capability from the healthy state to the unhealthy state:
determining that a flock for a second service is dependent on the first capability, and
delaying a release of the flock for the second service.
2. The method of claim 1 , wherein the functionality associated with the first service corresponds to a resource associated with the first service.
3. The method of claim 1 wherein the association between the alarm and the first capability is declared in a flock configuration for the first service, the flock configuration identifying a set of resources associated with the first service.
4. The method of claim 3 , wherein the flock configuration identifies one or more parameters related to the first service and a configuration setting for at least one resource related to the first service.
5. The method of claim 1 , further comprising:
determining that the release of the flock for the second service has been delayed; and
outputting a message identifying the first capability and the unhealthy state of the first capability as a reason for delay of the release of the flock for the second service.
6. The method of claim 5 , further comprising:
retrying the release of the flock for the second service upon determining that the state of the first capability is healthy.
7. The method of claim 1 , further comprising:
responsive to changing the state of the first capability to unhealthy:
determining one or more dependent capabilities that are dependent upon the first capability whose state is changed from healthy to unhealthy; and
changing the state of each of the one or more dependent capabilities to unhealthy.
8. The method of claim 1 , wherein the monitoring is performed by a telemetry service.
9. The method of claim 1 , further comprising:
creating an association between the alarm and a second capability, the second capability corresponding to a functionality associated with a second service, wherein the second service is different from the first service.
10. The method of claim 1 , further comprising:
identifying a set of one or more capabilities published in a data center that are marked as healthy and that are associated with the alarm; and
changing the state of each capability in the set of one or more capabilities from healthy to unhealthy.
11. The method of claim 1 , further comprising:
scheduling a release of the flock for the second service upon determining that the state of the first capability has changed from unhealthy to healthy.
12. A method comprising:
determining a set of direct capabilities for a flock configuration of a flock for which a release is to be scheduled;
identifying a set of indirect capabilities that depend from the set of direct capabilities;
determining a set of alarms associated with at least one of the set of direct capabilities or the set of indirect capabilities;
monitoring a set of alarm states for the set of alarms;
determining that at least one alarm of the set of alarms is in a triggered state based on the monitoring;
responsive to determining that the at least one alarm is in the triggered state, changing a state of the set of direct capabilities and the set of indirect capabilities associated with the at least one alarm that is in a triggered state from a healthy state to an unhealthy state; and
responsive to changing the state of the set of direct capabilities and the set of indirect capabilities from the healthy state to the unhealthy state:
determining that a flock for a second service is dependent on at least one capability of the set of direct capabilities and the set of indirect capabilities, and
delaying a release of the flock for the second service.
13. The method of claim 12 , further comprising:
updating the state of the set of direct capabilities and the set of indirect capabilities from a healthy state to an unhealthy state.
14. A system comprising:
a memory, the memory storing an association between an alarm and a first capability, the first capability corresponding to a functionality corresponding to a set of resources for a first service; and one or more processors configured to:
identify the association between the alarm and the first capability, wherein the first capability corresponds to the functionality associated with the first service;
monitor the alarm;
determine that the alarm is in a triggered state based on the monitoring;
responsive to determining that the alarm is in a triggered state, change a state of the first capability from a healthy state to an unhealthy state; and
responsive to changing the state of the first capability from the healthy state to the unhealthy state:
determine that a flock for a second service is dependent on the first capability, and
delay a release of the flock for the second service.
15. The system of claim 14 , wherein the functionality associated with the first service corresponds to a resource associated with the first service.
16. The system of claim 14 herein the association between the alarm and the first capability is declared in a flock configuration for the first service, the flock configuration identifying a set of resources associated with the first service.
17. The system of claim 16 , wherein the flock configuration identifies one or more parameters related to the first service and a configuration setting for at least one resource related to the first service.
18. The system of claim 14 , further comprising:
determine that the release of the flock for the second service has been delayed; and
output a message identifying the first capability and the unhealthy state of the alarm as a reason for delay of the release of the flock for the second service.