Changelog

Bug Fixes

• Filtering traces by trace ID in the list view no longer returns duplicate spans or results from outside the selected time window. Previously, the trace_summary timerange override was applied incorrectly across query buckets, causing repeated and out-of-range results.
• Logs pipeline filters now correctly resolve manually entered attribute names that are not present in the filter suggestion dropdown. Previously, entering a field like ddtags Exists by hand would misclassify it as a column rather than an attribute, causing downstream processors such as regex parsers to fail silently.
• The normalize pipeline now runs first in the processing chain, ensuring consistent field formatting before other pipelines execute.
• PromQL queries that exceed the execution deadline now return a 504 Gateway Timeout instead of a misleading 400 Bad Request. The PromQL engine timeout is also now configurable via the prometheus.timeout setting (default: 2m).
• Charts on the Volume Details page in Infrastructure Monitoring now display proper legend labels instead of "undefined."
• Domain rows in External APIs now show a pointer cursor on hover, indicating they are clickable.
• Time series charts with isolated data points surrounded by null values on both sides render those points correctly instead of dropping them.
• Deleting an alert rule or planned maintenance entry that has associated dependencies no longer fails with a foreign key constraint error.
• Agent configurations no longer get stuck in the "In Progress" state indefinitely.
• Users with the Editor role can now access gateway APIs as expected.
• Checkout and billing errors now surface the actual downstream error message in the UI instead of a generic failure.