Create an ingest token
Create the token that identifies your company when an application or a browser sends telemetry to APM, and revoke it when it's no longer used.
On this page
The token decides which company the data goes to. There are two types, each with a different use:
Type | What for | What it can send |
|---|---|---|
Server token | Back-end applications, processes, the OpenTelemetry Collector | Traces, metrics and logs |
Browser token | Code that runs in your users' web page | Traces only, only from the origins you specify and always with the same service name |
Never put a server token inside a web page: anyone who opens the page can read it. For the browser, always use a browser token.
Before you start
You need the Administer permission on the APM module.
APM must be active. See Enable APM.
Create a server token
Go to Settings → APM → API key and SDK.
On the Ingest tokens card, click Server token.
Enter a Name that identifies the system or server (for example, the application name and its environment).
Click Create.
Copy the token with Copy and keep it somewhere safe. Then click Done.
Create a browser token
Go to Settings → APM → API key and SDK.
In Ingest tokens, click Browser token.
Fill in:
Name: for example, "Customer portal".
Service name (fixed service.name): the name the website will have in APM. Only letters, numbers and
_ . : / -, no spaces.Allowed origins (one per line): the scheme and domain the page will load from, without a path. For example
https://portal.midominio.cl. Up to 20.
Click Create, copy the token and click Done.
The token is shown only once. ARGUNIS keeps only its fingerprint: if you lose it, create a new one and revoke the old one.
As long as you stay on the page, the How to instrument guides already include the newly created token and the ingest URL in the examples: you can copy the blocks as is.
Revoke a token
In Ingest tokens, find the token in the table.
Click the trash button in its row and confirm with Revoke.
Systems using it stop sending data in less than a minute. The token stays in the table as revoked, with its date.
What happens next
The table shows each token with its Type, Prefix, who created it and when, and its Last used. One token per system makes it easy to revoke just one if it leaks.