Skip to content
Last9 Last9

Ingestion Tokens

Create and manage tokens for sending telemetry data to Last9, including RUM and Prometheus metrics.

Control Plane — Ingestion Tokens

Ingestion Tokens authenticate your applications and services when sending telemetry data to Last9. These tokens control what data can be sent and from which origins, ensuring secure data collection.

Creating Ingestion Tokens

Control Plane — New Ingestion Tokens

  1. Select Token Type:

    • Client: For client-based data collection (eg: RUM)
    • Prometheus Remote-Write: For server-side Prometheus-compatible metrics
  2. Configure Client Type (if Client selected):

    • Web Browser: Default and currently available option for web applications
    • Mobile: Coming soon for mobile app monitoring
  3. Set Origins (for Client tokens):

    • Add the domains from which your application will send data
    • Example: https://www.example.com
    • Multiple origins can be added for multi-domain applications
    • Subdomain matching is not automatic, each subdomain needs separate entries
    ✅ Correct Origins:
    https://app.example.com
    https://www.example.com
    http://localhost:3000
    ❌ Incorrect Origins:
    example.com (missing protocol)
    *.example.com (wildcards not supported)
    app.example.com (missing protocol)
  4. Name Your Token:

    • Use a descriptive name to identify the token’s purpose
    • Example: “Production RUM Token” or “Staging Web Monitoring”
  5. Click CREATE TOKEN to generate your token


Troubleshooting

Please get in touch with us on Discord or Email if you have any questions.