Revision 42b50796
| b/doc/design-monitoring-agent.rst | ||
|---|---|---|
| 246 | 246 |
|
| 247 | 247 |
The instance status will be on each node, for the instances it is |
| 248 | 248 |
primary for, and its ``data`` section of the report will contain a list |
| 249 |
of instances, with at least the following fields for each instance: |
|
| 249 |
of instances, named ``instances``, with at least the following fields for |
|
| 250 |
each instance: |
|
| 250 | 251 |
|
| 251 | 252 |
``name`` |
| 252 | 253 |
The name of the instance. |
| ... | ... | |
| 269 | 270 |
|
| 270 | 271 |
``state_reason`` |
| 271 | 272 |
The last known reason for state change of the instance, described according |
| 272 |
to the JSON representation of a reason trail, as detailed in the :doc:`reason trail
|
|
| 273 |
design document <design-reason-trail>`. |
|
| 273 |
to the JSON representation of a reason trail, as detailed in the :doc:`reason |
|
| 274 |
trail design document <design-reason-trail>`.
|
|
| 274 | 275 |
|
| 275 | 276 |
``status`` |
| 276 | 277 |
It represents the status of the instance, and its format is the same as that |
Also available in: Unified diff