Skip to content

Commit 881c04e

Browse files
Merge pull request #1605 from StackVista/stac-22541-fix
STAC-22541: Update binding name and add extra one
2 parents 8097005 + 2f62140 commit 881c04e

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

use/alerting/k8s-derived-state-monitors.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,11 @@ A Monitor implemented using the `derived-state-monitor` function looks like:
3131
arguments:
3232
componentTypes: "deployment, replicaset, statefulset, daemonset"
3333
intervalSeconds: 30
34-
remediationHint: "Investigate component [{{ causeName }}](/#/components/{{ causeComponentUrnForUrl }}) as is causing the workload to be unhealthy."
34+
remediationHint: "Investigate component [{{ causeComponentName }}](/#/components/{{ causeComponentUrnForUrl }}) as is causing the workload to be unhealthy."
3535
```
3636
* The function has a single argument `componentTypes` where you can express the different component types as a single string of `,` separated values
37-
* 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
37+
* The function offers three values to use in the remediation guide
38+
* `componentName` being the name of the logical component.
39+
* `causeComponentName` being the component name where the state is propagated from and its `causeComponentUrnForUrl` to be able to create a link.
3840

3941
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)

0 commit comments

Comments
 (0)