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
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,9 @@ If Logs stack monitoring is configured for a Beat, and custom container argument

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

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:
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.

The 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:

```yaml
apiVersion: elasticsearch.k8s.elastic.co/v1
Expand All @@ -143,7 +145,7 @@ spec:
```

1. The `secretName` and `name` attributes are mutually exclusive, you have to choose one or the other.
2. The `namespace` and `serviceName` attributes can only be used in conjunction with `name`, not with `secretName`.
2. The `namespace` and `serviceName` attributes can only be used in conjunction with `name`, not with `secretName`, and only to reference clusters managed by the same ECK instance.

The referenced Secret must contain the following connection information:

Expand Down Expand Up @@ -193,4 +195,4 @@ spec:
- name: filebeat
env:
- foo: bar
```
```
Loading