check
and it can:example
that sends topology into StackState. It uses docker to run the StackState agent to execute the check.stackstate.yaml
file is the main agent configuration file. It tells the agent where to find StackState and what API key to use.example
check consists of two files:conf.d/example.d/conf.yaml
-- the check configuration filechecks.d/example.py
-- the check Python coderun.sh
shell script that runs the StackState agent in a docker container. It reads the configuration from this sample project and executes the example
check.stackstate.yaml
file) so it is fairly verbose.example
check will be sent to StackState.ctrl-c
to stop the agent.example
label. This should result in a topology similar to the following:example
agent check. The components appear in the Example domain and Applications and Hosts layers. The check produces two application components that StackState has grouped together. This is shown as a hexagon icon. Click on the group to access the individual components that make up the group.tags.related
= application_id_1
example.gauge
by Mean
streams
property in the Template function text area and copy it to your clipboard.example-example://example-1-component-template
in the Template dropdown.streams
part with the code you copied earlier.tags.related
key and some-application-1
for the value. This is correct for one of our components, but not for the other. We need to make this value dynamic.some-application-1
with a reference to the component's external id:Synchronization example example://example-1
synchronization.logstream
and its type is, indeed, Log stream
.host
= host_fqdn
CRITICAL
:alert_level
field in the custom-event.json
file to try out different values, such as error
, warning
and ok
. The component should change it's state a few seconds after receiving the event.CRITICAL
, this is what you should see: