Regarding Traffic FIlters in ES Cloud, the documentation reads the following:
This only applies to external traffic. Internal traffic is managed by Elasticsearch Service. For example, Kibana can connect to Elasticsearch, as well as internal services which manage the deployment. Other deployments can’t connect to deployments protected by traffic filters. Given the limitation, clusters used for monitoring, storing leader indices for cross-cluster replication or search across as part of cross-cluster search cannot be configured with traffic filters.
I'm currently testing this feature, and we have a dedicated monitoring cluster. Correct me if I'm wrong, but the documentation says that the monitoring cluster will not be able to monitor the production cluster, if the production cluster has traffic filters enabled?
If this is correct, then how come I can still see logs and monitoring data coming in from the production cluster, after activating a functional traffic filter?
What I did encounter was that Watcher alerts that used curl against the production cluster endpoint failed, but Alerting still works as it looks in the monitoring indecies rather than curling the production cluster health/stats API.
I hope someone can shed some light on this, or clarify the documentation in some way.