TimeKeeper can be used as a client, server, grandmaster, compliance tool, and more. Other sections of this documentation cover specifics of features related to those scenarios. Here the focus is on introducing TimeKeeper in narrow configurations, starting as a client, in order to concentrate on core principles.
In order to focus on the core idea of each recipe, extra options that would be seen in a typical deployment are generally omitted. For example, when failing over between sources an SNMP trap host might be configured to send alerts about the change. A recipe about failover will omit those SNMP configuration details to focus on the core feature at hand, which is failover.
Please refer to either other recipes or other sections of the documentation for broader coverage of all of the options TimeKeeper offers.