charm_logging not setting juju_topology labels

[amandahla]

Bug Description

I'm trying to create Loki alert rules for logs collected by log_charm but I noticed that they are pushed with labels like this:

{application="maubot", charm_name="maubot", juju_hook_name="config-changed", logger="root", model="testing4", model_uuid="5c4acb0e-4b2e-4c07-8eee-f5cd5d968a4d", service_name="maubot", severity="error", unit="maubot/0"}

And I was expecting to use %%juju_topology%% so the labels would be something like:

{charm="maubot", juju_application="maubot", juju_model="testing4", juju_model_uuid="5c4acb0e-4b2e-4c07-8eee-f5cd5d968a4d", juju_unit="maubot/0", pebble_service="maubot", product="Juju"}

Am I missing something?

To Reproduce

canonical/maubot-operator#21

Environment

$ juju status
Model     Controller          Cloud/Region        Version  SLA          Timestamp
testing4  microk8s-localhost  microk8s/localhost  3.5.3    unsupported  16:11:52-03:00

App             Version  Status  Scale  Charm           Channel        Rev  Address         Exposed  Message
grafana-k8s     9.5.3    active      1  grafana-k8s     latest/edge    120  10.152.183.146  no       
loki-k8s        2.9.6    active      1  loki-k8s        latest/edge    173  10.152.183.55   no       
maubot                   active      1  maubot                          12  10.152.183.239  no       
postgresql-k8s  14.12    active      1  postgresql-k8s  14/stable      381  10.152.183.122  no       
prometheus-k8s  2.52.0   active      1  prometheus-k8s  latest/stable  209  10.152.183.205  no       
s2              1.116.0  active      1  synapse                          8  10.152.183.100  no       

Relevant log output

No log.

Additional context

No response

[Abuelodelanada]

We should compare the labels we set to the ones we get from LogProxyConsumer and PebbleLogForwarding