No traces showing up

If you sent a trace but nothing appears in the UI, work through this checklist.

1) Confirm environment variables

• BOSON_API_KEY is set in the process that runs your app
• BOSON_HOST is correct (only change it if your organization uses a customer-deployed Boson URL, not Boson Cloud’s default)

Tip: print whether the variables are present (never print the key value).

2) Make sure you end the trace

Traces often appear only after you call trace.end(). Ensure it is called in finally so errors still flush.

3) Network egress

• can your runtime reach the Boson host?
• are proxies, VPC rules, or corporate firewalls blocking egress?

4) Time and clock skew

If timestamps are far off, traces may be hard to find. Ensure the host’s clock is synced (NTP).

5) Sampling rules

If you introduced sampling, confirm error traces are still captured and that your sampled rate isn’t 0%.

Next steps

• Authentication errors