While looking into T359497: StatsD Exporter: gracefully handle metric signature changes I stumbled upon the fact that metrics conflicts are reported for Thumbor' statsd-exporter, i.e.

sum by (job, app,cluster) (rate(statsd_exporter_events_conflict_total[5m]) > 0)

This can happen when metrics of different types are sent to statsd-exporter (e.g. the same metric is sent as a counter and as a gauge).

I don't know Thumbor's plans (in general) and specifically for metrics, in other words feel free to resolve the task if fixing this bug isn't on the roadmap!