Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions use/alerting/k8s-derived-state-monitors.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,9 +31,11 @@ A Monitor implemented using the `derived-state-monitor` function looks like:
arguments:
componentTypes: "deployment, replicaset, statefulset, daemonset"
intervalSeconds: 30
remediationHint: "Investigate component [{{ causeName }}](/#/components/{{ causeComponentUrnForUrl }}) as is causing the workload to be unhealthy."
remediationHint: "Investigate component [{{ causeComponentName }}](/#/components/{{ causeComponentUrnForUrl }}) as is causing the workload to be unhealthy."
```
* The function has a single argument `componentTypes` where you can express the different component types as a single string of `,` separated values
* The function offers two values to use in the remediation guide, `causeComponentName` being the component name where the state is propagated from and its `causeComponentUrnForUrl` to be able to create a link
* The function offers three values to use in the remediation guide
* `componentName` being the name of the logical component.
* `causeComponentName` being the component name where the state is propagated from and its `causeComponentUrnForUrl` to be able to create a link.

The monitor can be implemented using the guide at [Add a threshold monitor to components using the CLI](/use/alerting/k8s-add-monitors-cli.md)