-
Notifications
You must be signed in to change notification settings - Fork 1
/
config.example.yaml
68 lines (60 loc) · 3.06 KB
/
config.example.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
### An example of configuration file for siera-kube-watch
webhook:
enabled: true
url: "http://127.0.0.1/webhook"
### Enable dead man's switch functionality, similar to https://docs.openshift.com/container-platform/3.11/install_config/prometheus_cluster_monitoring.html#dead-mans-switch_prometheus-cluster-monitoring
livenesscheck:
enabled: true
interval: "2s"
### For more information, refer to https://api.slack.com/messaging/webhooks
slack:
enabled: true
### slack url contain webhook url for your workspace.
### Example:
### url: "https://hooks.slack.com/services/TOKEN"
### username: "Siera Kube Watch" [OPTIONAL]
### channel: "#siera" [OPTIONAL]
url: "https://hooks.slack.com/services/TOKEN"
### For more information, refer to https://core.telegram.org/bots/api
telegram:
enabled: true
### token is a unique authentication token when a bot is created.
### Example:
### token: "123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11"
token: "123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11"
### chatID is a string contain unique identifier for the target chat or username of the target channel (in the format
### @channelusername).
### Example:
### chatID: "-1234567890123"
chatID: "-1234567890123"
### For more information, refer to https://developers.facebook.com/docs/workplace/bots/
workplace:
enabled: false
### thread.key is unique identifier of an existing group chat thread.
### Example:
### thread.key: "t_123456789"
thread.key: "t_123456789"
### token is a generated access token when you create a new app for Workplace.
### For more information, refer to https://developers.facebook.com/docs/workplace/reference/permissions/
### Example:
### token: "ABCDEF123456"
token: "ABCDEF123456"
### In case you want to filter your event stream from specific reason, you can add that reason to excluded.reasons.
### excluded.reasons is an array of reasons that will be excluded so any event that have one of these reasons won't be
### published.
### Example:
### excluded.reasons: ["FailedGetResourceMetric", "ScalingReplicaSet", "Started", "Killing", "Unhealthy"]
excluded.reasons: []
### For filtering purpose, by default we excluded normal events (to avoid noisy channel) but if needed you can include
### several reasons from normal event for investigation purpose.
### included.reasons is an array of reasons that will be included from normal events.
### Example:
### included.reasons: ["ScalingReplicaSet", "SuccessfulCreate", "SuccessfulDelete"]
included.reasons: ["ScalingReplicaSet", "Started", "Killing"]
### By default we include event from all namespaces, but you can filter namespace that you want to watch for.
### included.namespaces is an array of specific namespaces that will be included instead of publishing all namespaces.
### Example:
### included.namespaces: ["my-namespace", "your-namespace"]
### If you want to add this configuration, you can uncomment this field (by removing `#` in front of this
### configuration) and set whatever value you wish.
# included.namespaces: []