@JMeybohm - Do you think this is something we could make meaningful progress on this quarter?

I'm thinking the monitoring improvement (T422955) might be slightly higher priority in the short term (i.e., if it's a choice between them), but I'm also not sure how much work some of the known low-hanging fruit here might be (e.g., mesh configuration).

In T422967#11829941, @Scott_French wrote:

@JMeybohm - Do you think this is something we could make meaningful progress on this quarter?

I'm thinking the monitoring improvement (T422955) might be slightly higher priority in the short term (i.e., if it's a choice between them), but I'm also not sure how much work some of the known low-hanging fruit here might be (e.g., mesh configuration).

I think we should at least do the mesh config changes (and chart module updates) ASAP since it takes quite some time for them to roll out naturally.

Great, thanks @JMeybohm - Do you have a sense of what the highest-priority changes to the mesh configuration may be? i.e., some combination of dns_refresh_rate or respect_dns_ttl?

In T422967#11853354, @Scott_French wrote:

Great, thanks @JMeybohm - Do you have a sense of what the highest-priority changes to the mesh configuration may be? i.e., some combination of dns_refresh_rate or respect_dns_ttl?

I was more aiming towards adding the dot-suffix throughout the mesh config, eliminating a bunch of unnecessary DNS queries without changing the behavior otherwise.
In a second step we could look at respect_dns_ttl which feels like the more natural choice compared to changing the static dns_refresh_rate.

Ah, got it - thanks, @JMeybohm. For some reason, I thought there was something else beyond the dot-suffixing being proposed. In any case, +1 to starting with just the dot-suffixing, as it's clearly beneficial and implies minimal behavior change.