Skip to content

fix(runner/chronosphere): honor CHRONOSPHERE_TRACES_URL on the query path - #530

Open
mayankpande88 wants to merge 3 commits into
mainfrom
fix/runner-chronosphere-traces-url
Open

fix(runner/chronosphere): honor CHRONOSPHERE_TRACES_URL on the query path#530
mayankpande88 wants to merge 3 commits into
mainfrom
fix/runner-chronosphere-traces-url

Conversation

@mayankpande88

Copy link
Copy Markdown
Contributor

The chronosphere_query_traces handler always posted to
BaseURL + /api/v1/data/traces, ignoring CHRONOSPHERE_TRACES_URL — which
the legacy chronosphere_client used verbatim as the traces search
endpoint. CHRONOSPHERE_TRACES_URL was only read for the telemetry
heartbeat, so a deployment relying on that override hit the wrong path.

Add a TracesURL field on the client (fed from CHRONOSPHERE_TRACES_URL):
use it verbatim when set, else fall back to the composed BaseURL path.
Also enable the handler when either CHRONOSPHERE_URL or
CHRONOSPHERE_TRACES_URL is set, so a traces-URL-only config still
registers the action.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01L2HAXQH1gEtX7h4sUJsi9j

@mayankpande88
mayankpande88 requested a review from a team as a code owner July 14, 2026 19:29

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces support for overriding the Chronosphere traces search endpoint via the CHRONOSPHERE_TRACES_URL environment variable. The agent now registers the Chronosphere proxy if either the base URL or the explicit traces URL override is set. Feedback suggests updating the error message in QueryTraces to accurately reflect when neither URL is configured.

Comment thread runner/pkg/observability/chronosphere/client.go
@github-actions

Copy link
Copy Markdown
Contributor

📦 Image Tags Updated

I've automatically updated the image tags in `charts/nudgebee-agent/values.yaml` to the latest versions from GHCR for the `main` branch.

The image tags are now synchronized with the latest builds and ready for release.

RamanKharchee
RamanKharchee previously approved these changes Jul 15, 2026
@mayankpande88
mayankpande88 force-pushed the fix/runner-chronosphere-traces-url branch 2 times, most recently from 2d20cb3 to 50de22e Compare July 15, 2026 09:42
…path

The chronosphere_query_traces handler always posted to
BaseURL + /api/v1/data/traces, ignoring CHRONOSPHERE_TRACES_URL — which
the legacy chronosphere_client used verbatim as the traces search
endpoint. CHRONOSPHERE_TRACES_URL was only read for the telemetry
heartbeat, so a deployment relying on that override hit the wrong path.

Add a TracesURL field on the client (fed from CHRONOSPHERE_TRACES_URL):
use it verbatim when set, else fall back to the composed BaseURL path.
Also enable the handler when either CHRONOSPHERE_URL or
CHRONOSPHERE_TRACES_URL is set, so a traces-URL-only config still
registers the action.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L2HAXQH1gEtX7h4sUJsi9j
(cherry picked from commit 50de22e)
@mayankpande88

Copy link
Copy Markdown
Contributor Author

Rebased onto main: merged the TracesURL override into the retry/concurrency-limited client that landed on main since approval (tracesEndpoint() now used by doQuery). Package tests pass. Please re-approve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants