User Templates

The custom adapter must contact an external service. For example, LDAP server and JMS services.

  • The external resource configuration will be common to all end points and pre and post inputs.
  • If the custom configuration file is not available, users will have to replicate the configuration in all endpoint as pre and post inputs.
  • Container/pod specific resources must be placed in specific directories.
  • If a file or resource is required in more than one container, a copy must exist in directories meant for every container.
  • Input the value for place holders in the templates of the respective container type properties.
  • Before bringing up the cluster, copy the custom resources or configuration templates to the specific directories at <extract directory>/docker-deploy/resources/<tml-type>.
  • The resources for each of the containers must be accompanied by a specification file in json format. The json file has to be named usertemplate_config.json. If user has content for more than one container type, each container type should have the spec file.

    The structure of the usertemplate_config.json must be as follows.

Note: For td-agent templates in log container, specification file is not required. The template will be used as configuration file.