Skip to content
Snippets Groups Projects
Commit 42b50796 authored by Michele Tartara's avatar Michele Tartara
Browse files

Monitoring design doc: better specify field names


The name of the list of instances was not specified.

Also, fix a line that was longer than 80 characters.

Signed-off-by: default avatarMichele Tartara <mtartara@google.com>
Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
parent 6ab6b19a
No related branches found
No related tags found
No related merge requests found
...@@ -246,7 +246,8 @@ upon. ...@@ -246,7 +246,8 @@ upon.
The instance status will be on each node, for the instances it is The instance status will be on each node, for the instances it is
primary for, and its ``data`` section of the report will contain a list primary for, and its ``data`` section of the report will contain a list
of instances, with at least the following fields for each instance: of instances, named ``instances``, with at least the following fields for
each instance:
``name`` ``name``
The name of the instance. The name of the instance.
...@@ -269,8 +270,8 @@ of instances, with at least the following fields for each instance: ...@@ -269,8 +270,8 @@ of instances, with at least the following fields for each instance:
``state_reason`` ``state_reason``
The last known reason for state change of the instance, described according The last known reason for state change of the instance, described according
to the JSON representation of a reason trail, as detailed in the :doc:`reason trail to the JSON representation of a reason trail, as detailed in the :doc:`reason
design document <design-reason-trail>`. trail design document <design-reason-trail>`.
``status`` ``status``
It represents the status of the instance, and its format is the same as that It represents the status of the instance, and its format is the same as that
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment