[abnegate]

What does this PR do?

instrument() used the request method as a Prometheus label on exiftool_http_requests_total and exiftool_http_request_duration_seconds. Routes are already normalized by telemetryRoute(); methods were not, so each distinct method token created a new series.

This maps the method label to the standard HTTP methods and folds anything else into other, keeping method-label cardinality bounded. The structured request log still records the original method, truncated when it is unusually long.

Test Plan

• Regression test sends 64 distinct non-standard methods plus GET and POST, then asserts both HTTP metrics keep a bounded method-label set (GET, POST, and other).
• Unit tests for telemetryMethod and loggedMethod.
• go test -race ./..., go vet ./..., and gofmt on the changed files.

  

[abnegate]

@hansi-codes review

[hansi-codes]

🟢 Tier S · Ready to merge

The changed behavior is bounded as intended and has direct regression coverage.

HTTP request metrics now normalize methods to a fixed set of standard methods plus an other bucket. Request-completion logs retain the original method while truncating unusually long values, and new tests cover the normalization, truncation, and metric-label cardinality.

Verdict	New comments	Fixed	Still open
✅ Approved	0	0	0

📂 Walkthrough · 2

File	Change
cmd/exiftool-server/telemetry.go	Normalize method labels for HTTP metrics and bound the method value written to request logs.
cmd/exiftool-server/telemetry_test.go	Add tests for bounded metric method labels, method normalization, and log truncation.

---

_{Reviewed 5852c49 · Details · Comment @hansi-codes review to re-run, or mention @hansi-codes with a question.}

[hansi-codes]

🟢 Tier S · Looks good to merge. Summary