Verify your setup

Do this verification after instrumenting the first application and after any material SDK or collector configuration change.

Send a recognizable test

Use a unique customer ID and error message so you do not confuse the test with real traffic.

distinct_id: teml-verification-user
error:       teml verification error
environment: development

If your SDK buffers data, stop it gracefully or call its flush method before ending a short-lived test process.

Check the customer first

1. Select the expected project and environment.
2. Open Customers.
3. Search for teml-verification-user.
4. Confirm the customer has recent activity.
5. Open the timeline and confirm the error and trace point to the same customer.

Finding a trace without finding the customer means ingestion works but identity is incomplete. See Customer activity is not connecting.

Check the Issue

Open Issues and search for the test error. Confirm that:

• the occurrence is grouped under one Issue;
• the affected customer is present;
• the trace link opens the expected request; and
• a replay is linked when browser replay is enabled.

Check investigation

Open Investigate and ask a narrow question using the test identifier:

What happened to teml-verification-user in the last hour?

The answer should cite the evidence you just inspected manually. A grounded answer with no matching evidence usually means the project, environment, or time window is wrong.

Roll out only after this passes

Once the full path works, add the next service or application. Preserve the same stable customer ID and propagate it only across trusted internal boundaries. Re-run this check after each expansion.