From 7d6f30da1cad3d7d57c7c7900825b8a41a5a15cf Mon Sep 17 00:00:00 2001 From: Shawn Cook Date: Fri, 11 Sep 2015 14:27:54 -0700 Subject: [PATCH] Docs - add verbage to anti-entropy page. --- website/source/docs/agent/services.html.markdown | 3 ++- .../docs/internals/anti-entropy.html.markdown | 14 ++++++++++++++ 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/website/source/docs/agent/services.html.markdown b/website/source/docs/agent/services.html.markdown index b9e13645b..c64cb68ee 100644 --- a/website/source/docs/agent/services.html.markdown +++ b/website/source/docs/agent/services.html.markdown @@ -90,7 +90,8 @@ the same service their `enableTagOverride` configuration and all other service configuration items are independant of one another. Updating the tags for the service registered on one node is independant of the same service (by name) registered on another node. If `enableTagOverride` is not specified the default -value is false. +value is false. See [anti-entropy syncs](/docs/internals/anti-entropy.html) +for more info. To configure a service, either provide it as a `-config-file` option to the agent or place it inside the `-config-dir` of the agent. The file must diff --git a/website/source/docs/internals/anti-entropy.html.markdown b/website/source/docs/internals/anti-entropy.html.markdown index 50d42819c..69a78bbe9 100644 --- a/website/source/docs/internals/anti-entropy.html.markdown +++ b/website/source/docs/internals/anti-entropy.html.markdown @@ -135,3 +135,17 @@ fashion. If an error is encountered during an anti-entropy run, the error is logged and the agent continues to run. The anti-entropy mechanism is run periodically to automatically recover from these types of transient failures. + +### EnableTagOverride + +Synchronization of service registration can be partially modified to allow +external agents change the tag value of a service. This can be useful in +situations where an external monitoring service needs to be the source of +truth for tag information. For instance: Redis DB and its monitoring service +Redis Sentinel have this kind of relationship. Redis instances are responsible +for much of their configuration, but Sentinels determine whether the Redis +instance is a master or a slave. Using the Consul service configuration item +[EnableTagOverride](/docs/agent/services.html) you can instruct the Consul +agent on which the Redis DB is running to NOT update the tags during anti-entropy +synchronization. For more information see [Services](/docs/agent/services.html) +page.