DocumentaciónHelp

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

  1. Go to Settings → APM → API key and SDK.

  2. On the Ingest tokens card, click Server token.

  3. Enter a Name that identifies the system or server (for example, the application name and its environment).

  4. Click Create.

  5. Copy the token with Copy and keep it somewhere safe. Then click Done.

Create a browser token

  1. Go to Settings → APM → API key and SDK.

  2. In Ingest tokens, click Browser token.

  3. 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.

  4. 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

  1. In Ingest tokens, find the token in the table.

  2. 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.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close