Jaeger UI max lookback getting overriden by the custom time range

[aujjwal-smarsh]

Hi folks,

I am using Jaeger v2 for running my Jaeger resources in K8s. I had updated the Jaeger UI config file with the following changes:

{
      "search": {
        "maxLookback": {
          "label": "2 Hours",
          "value": "2h"
        },
        "maxLimit": 2000
      }

On the UI, the max lookback is now showing at max 2 hours, but the custom range is still able to query any time window greater than 2 hours. Is this expected, or am I missing something in the config?

Use-case

• Users should not be able to query data for a time window > 2 hours to prevent overloading our underlying storage backend.

[dosubot[bot]]

Yes, this is expected behavior. The Jaeger UI's maxLookback setting only restricts the preset lookback options shown in the UI—it does not enforce a hard limit on custom time range queries. Users can still select custom ranges beyond the configured max lookback, and the backend does not enforce a maximum query window either. There is currently no built-in way to enforce a hard limit on the maximum queryable time window for custom ranges in Jaeger UI or the backend. Enforcing such a limit would require changes to the backend query service or storage implementation to validate and restrict incoming queries based on their time range [source].

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[aujjwal-smarsh]

This would make the management difficult since we cannot expect the end user not to override the max lookback. This could easily overload the underlying storage, like ES.