2. Getting started
Requirements
- A Dynatrace SaaS Tenant with DPS license (sign up here)
- Live, Sprint, or Dev environment
- Full administrator access to the account and tenant
- A GitHub account to interact with the demo repository and run a Codespaces instance
- Codespaces core-hours and storage available (GitHub Billing & Licensing)
Prerequisites#
- Identify Dynatrace OTLP Endpoint
- Generate Dynatrace Access Token
- Identify Your Initials
- Add Bucket Storage Management Permissions
Identify Dynatrace OTLP Endpoint#
The OpenTelemetry Protocol (OTLP) is the principal network protocol for the exchange of telemetry data between OpenTelemetry-backed services and applications. The Dynatrace SaaS tenant provides an OTLP endpoint.
See Related Export with OTLP Documentation
Identify and save/store your OTLP endpoint for the Dynatrace SaaS tenant:
No Trailing Slash
Do not include a trailing slash!
| Type | URL Pattern |
|---|---|
| Live (Prod) | https://{your-environment-id}.live.dynatrace.com/api/v2/otlp |
| Stage | https://{your-environment-id}.sprint.dynatracelabs.com/api/v2/otlp |
| ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/v2/otlp |
Generate Dynatrace Access Token#
Generate a new API access token with the following scopes:
Ingest events
Ingest logs
Ingest metrics
Ingest OpenTelemetry traces
Identify Your Initials#
In this lab, we'll uniquely identify your OpenTelemetry data using your initials; in case you are using a shared tenant. We'll be using <INITIALS>-k8s-otel-o11y as our pattern. Identify your initials (3-5 characters) and use them whenever prompted during the lab.
Add Storage Management Permissions#
The Grail data model consists of buckets, tables, and views. Records are stored in buckets. Buckets are assigned to tables, including logs, metrics, events, security events, and bizevents tables. Fetching from a table returns all records from all buckets that are assigned to that table. To manage your buckets, ensure that you have configured the following permissions:
- storage:bucket-definitions:read
- storage:bucket-definitions:write
- storage:bucket-definitions:delete
- storage:bucket-definitions:truncate
Policy definition:
ALLOW storage:bucket-definitions:write;
ALLOW storage:bucket-definitions:read;
ALLOW storage:bucket-definitions:delete;
ALLOW storage:bucket-definitions:truncate;
After creating the policy, be sure to add/bind it to a group that you belong to.