salt-teagentfolder downloaded from GitHub:
top.sls) contains the hierarchy of nodes in an environment and can allow or limit communication to nodes when running modules. If you don't have a Topfile, you can use the example provided by moving it into the salt folder:
top.slsfile then you can add the statement
thousandeyes.te-agentto the desired environment. Below is an example to make the module available for any nodes in the base environment:
/srv/salt/thousandeyes/te-agent.conf.yml. Modify the configuration file in the root folder to alter any of the default settings. Below is a list of the fuction variables and their possible states.
test.pingis the easiest way to check the connection. Unlike a regular ICMP ping, the function
test.pingattempts to establish a TCP connection and reports either
False. In the example below, all salt-minions are targeted. For larger deployments this obviously wouldn't make sense. Replacing the * with the salt-minion's ID is the easiest way to target a single node.
top.slsfile which, by default, is
top.slsfile. Here is where you can restrict which salt-minions are affected. Some common limitations include matching an operating system or salt-minion ID.
top.slsconfiguration file so that minions are in the desired environments. In the following example, all salt-minions with a name that starts with
production-will receive the production configuration file
thousandeyes.te-agent-production(note the absence of the
test.pingcommand this could be a firewall issue. Check SaltStack firewall documentation below.
# salt-master -l debug