[Bug]: telemetry in msg handlers runs multiple times leading to unexpected metric values

[migueldingli1997]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Message logic is executed at least twice, once in checkTx and once during block finalization. Telemetry logic does not distinguish between these two modes and runs regardless, meaning that counters are incremented at least twice.

One example of this is the new_account counter which is incremented when we send tokens to a new account. The result is that this counter actually increments by 2 with each new account.

I suppose it could increment even more times if we run in other modes, such as to simulate a transaction, but I haven't experimented with this.

Cosmos SDK Version

0.50.9

How to reproduce?

• Run a chain with Prometheus telemetry enabled
• Send tokens to an account that does not exist
• Look up the new_account metric at :1317/metrics?format=prometheus