You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using orchestrator with instance aliases, in this way we can have both ip address and hostname information of our instances in orchestrator.
But we have some automated pipelines which create new mysql instances to make recovery and replication restore tests. We do not want to see these test instances on orchestrator . But orchestrator discovers them automatically when they are connected as replica to mysql cluster. after they are destroyed by pipeline orchestrator sees them as dead replicas.
We have realised orchestrator has a filter called DiscoveryIgnoreHostnameFilters which runs hostname based . But since we don't use orchestrator's hostname and mysql hostname resolve methods orchestrator has ip addresses of our instances in hostname field in instance metadata. So the following config is not working because of this. Because this filter does not care instance alias and orchestrator trying to find filter keyword in ip addresses.
harunkucuk5
changed the title
DiscoveryIgnoreHostnameFilters does not care instance aliases
DiscoveryIgnoreHostnameFilters do not care instance alias
Aug 26, 2021
Hi,
We have been using orchestrator with instance aliases, in this way we can have both ip address and hostname information of our instances in orchestrator.
But we have some automated pipelines which create new mysql instances to make recovery and replication restore tests. We do not want to see these test instances on orchestrator . But orchestrator discovers them automatically when they are connected as replica to mysql cluster. after they are destroyed by pipeline orchestrator sees them as dead replicas.
We have realised orchestrator has a filter called
DiscoveryIgnoreHostnameFilters
which runs hostname based . But since we don't use orchestrator's hostname and mysql hostname resolve methods orchestrator has ip addresses of our instances in hostname field in instance metadata. So the following config is not working because of this. Because this filter does not care instance alias and orchestrator trying to find filter keyword in ip addresses."DetectInstanceAliasQuery": "SELECT SUBSTRING_INDEX(@@hostname, '.', 1)",
"DiscoveryIgnoreHostnameFilters": ["auto-verify.*"],
to be able to make this filter work with aliases we need some improvements .
Thanks
The text was updated successfully, but these errors were encountered: