luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

website: clarify unique per-ndoe

This commit is contained in:
Armon Dadgar 2014-06-08 17:31:44 -07:00
parent c656bbfbcf
commit 0b87eb29de
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/docs/agent/checks.html.markdown
View File

@ -52,8 +52,8 @@ A TTL based check is very similar:
Both types of definitions must include a `name`, and may optionally
provide an `id` and `notes` field. The `id` is set to the `name` if not
provided. It is required that all checks have a unique ID, so if names
might conflict, then unique ID's should be provided.
provided. It is required that all checks have a unique ID per node, so if names
might conflict then unique ID's should be provided.
The `notes` field is opaque to Consul, but may be used for human
readable descriptions. The field is set to any output that a script

4
website/source/docs/agent/services.html.markdown
View File

@ -31,8 +31,8 @@ A service definition that is a script looks like:
A service definition must include a `name`, and may optionally provide
an `id`, `tags`, `port`, and `check`. The `id` is set to the `name` if not
provided. It is required that all services have a unique ID, so if names
might conflict, then unique ID's should be provided.
provided. It is required that all services have a unique ID per node, so if names
might conflict then unique ID's should be provided.
The `tags` is a list of opaque value to Consul, but can be used to distinguish
between "master" or "slave" nodes, different versions, or any other service level labels.