serializers.prometheusremotewrite should log which input caused the error

[llamafilm]

Use Case

I'm seeing occasional errors from this Prometheus output, but even with trace level logging there's no way to tell which input/measurement is causing this issue.

{"time":"2025-03-07T21:56:27.040555096Z","level":"TRACE","msg":"failed to parse "system_uptime_format": bad sample value " 0:30"","category":"serializers","plugin":"prometheusremotewrite::http"}
{"time":"2025-03-07T21:56:27.043952888Z","level":"ERROR","msg":"some series were dropped, 3212 series left to send; last recorded error: failed to parse "system_uptime_format": bad sample value " 0:30"","plugin":"prometheusremotewrite::http","category":"serializers"}

Expected behavior

Would it be possible to include the alias of the input which caused the problem?

Actual behavior

log shown above

Additional info

I'm using Telegraf 1.33.3. I guess these errors probably existed before, but I never noticed them until now because of #15893.

[llamafilm]

Doh! Sorry, never mind. I realized system is the measurement and uptime_format is the field.