Account & team

Your plan, trial or renewal date, and which modules are enabled.

Check here first whenever access stops working. An expired trial and a bad API key look identical from the agent's side, and this page tells the two apart immediately.

It is the one page that explains a 402. Knowing the subscription lapsed saves you debugging telemetry that was never the problem.

Create and revoke keys. A key is shown once, at creation. Only a hash is stored. The list shows the prefix, when it was created and when it was last used.

Create a key, copy it immediately, and set it as OTEL_EXPORTER_OTLP_HEADERS on your agent. See Connect your agent.

export OTEL_EXPORTER_OTLP_HEADERS="X-API-Key=tiq_your_key_here"

Issue one key per agent or environment rather than sharing one everywhere.

Separate keys make revocation surgical: killing a leaked key takes down one agent instead of all of them. “Last used” also tells you which keys are dead and safe to remove, which a shared key can never tell you.

Plan, payment history, upgrade and cancellation.

Upgrade or cancel from here. On cancellation, access continues until the end of the period you have already paid for, and then does not renew.

Being locked out of billing by a billing problem is a trap we deliberately avoided. Whatever else stops, the page that lets you fix it stays reachable.

Support tickets and feedback, raised from inside the console. Each ticket gets a reference such as TIQ-8F3A2B and a thread you can reply to.

Choose a ticket (issue, bug, billing, account) or feedback (improvement, new feature, general), write what happened, and send. Replies arrive by email and in the thread here.

For something quick, the Contact us button in the corner of every page sends a bug report, feature request or question without opening a ticket. You can also email traptureiq@techtrapture.com.

A ticket carries the account and tenant it came from, so we see your plan and setup before replying instead of asking for it first.

A tenant is one isolated workspace with its own database. Create one per team or per environment.

Create a tenant, then invite people by email with a role of admin or user. Switch tenants from the picker in the sidebar.

To point an agent at a shared tenant rather than your personal one, add the tenant id header. See Connect your agent.

export OTEL_EXPORTER_OTLP_HEADERS="X-API-Key=tiq_your_key_here,X-Tenant-Id=<tenant-id>"

Separate tenants keep staging noise out of production numbers, and let you give a team access to their own data without exposing everyone else's.