Comment 2 for bug 1952796

Quick comment on the relation count

Offer Application Charm Rev Connected Endpoint Interface Role
grafana grafana grafana 51 3/3 dashboards grafana-dashboard requirer
graylog-beats graylog graylog 50 1/1 beats elastic-beats provider <<<<--- 1/1 relations ?

When you relate a consuming application to the offer, there is only the one relation (aka connection) displayed; this is independent of how many units may be involved. It's no different to in-model relations in "juju status --relations" - only one item is shown per relation even if many units are involved.

Depending on what the exact issue is, it could be related to exactly what relation data is passed between the offering and consuming charm. We've seen in the past that charms can select an inappropriate address for example. We'd need to know exactly what's misconfigured, how it's misconfigured, where the config comes from, what's missing or incorrect etc etc to narrow down is it a juju issue, is it a charm issue etc etc.