# Investigating a Production Latency Increase Caused by Misleading Metrics

DevFeed: [Investigating a Production Latency Increase Caused by Misleading Metrics](<https://devfeed.tech/articles/how-to-get-fooled-by-metrics-28003.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2020-12-04-howtogetfooledbymetrics/>)

Author: Dominik Sandjaja

Published: 2020-12-04T00:00:00Z

Content type: opinion

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [incident](<https://devfeed.tech/tags/incident.md>), [latency](<https://devfeed.tech/tags/latency.md>), [logging](<https://devfeed.tech/tags/logging.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [production](<https://devfeed.tech/tags/production.md>)

## AI overview

A production feature intended to reduce hotel IDs in requests unexpectedly coincided with a 30% increase in median latency. The investigation found that the implementation reduced request size as intended, while the metrics were correct and had initially led the team toward the wrong explanation.

## Source excerpt

Metrics are one of the main building blocks in the topic of observability and we use them heavily. This story is about an incident where we tried to find and resolve a problem that we saw in these metrics. We went down a rabbit hole of potential fixes, only to discover that the metrics were correct all along.