Skip to content

Commit e4bf940

Browse files
Update eck-stack-monitoring.md
The example for "Connect to an external monitoring elasticsearch cluster" can lead to confusion or seem to be incorrect, so I added a small explanation about what the config in the example does
1 parent a08002e commit e4bf940

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,9 @@ If Logs stack monitoring is configured for a Beat, and custom container argument
116116

117117
## Connect to an external monitoring {{es}} cluster [k8s_connect_to_an_external_monitoring_elasticsearch_cluster]
118118

119-
If you want to connect to a monitoring {{es}} cluster not managed by ECK, you can reference a Secret instead of an {{es}} cluster in the `monitoring` section through the `secretName` attribute:
119+
If you want to connect to a monitoring {{es}} cluster not managed by ECK, you can reference a Secret instead of an {{es}} cluster in the `monitoring` section through the `secretName` attribute.
120+
121+
Next example sends cluster metrics to a remote monitoring cluster not managed by ECK, whereas cluster logs are sent to a remote cluster handled by ECK.
120122

121123
```yaml
122124
apiVersion: elasticsearch.k8s.elastic.co/v1
@@ -193,4 +195,4 @@ spec:
193195
- name: filebeat
194196
env:
195197
- foo: bar
196-
```
198+
```

0 commit comments

Comments
 (0)