Wrong juju_topology in alert rule provided via `LogProxyConsumer`

[rgildein]

Description

We are working on tempest-k8s charm, which is using the LogProxyConsumer for logs forwarding and the alert rule. If we do relation grafana-agent-k8s:logging-provider tempest-k8s:logging the alert rule, define in the LogProxyConsumer will have juju_topology from grafana-agent-k8s and not the tempest-k8s charm.

Example from my local deployment.

tempest model:

• grafana-agent-k8s rev. 51

cos model:

• alertmanager rev. 96
• catalogue rev. 33
• grafana rev. 93
• loki rev. 105
• prometheus rev. 159
• traefik rev. 166

Urgency

Blocker for our release

Python-libjuju version

not using libjuju

Juju version

3.1.6

Reproduce / Test

not using libjuju

[rgildein]

I opened this accidentally in the wrong repo.