Getting started with Uptrace
Getting started with Uptrace and OpenTelemetry is easy:
- To host Uptrace yourself, download and install Uptrace binary. Or create a free cloud account and let us manage Uptrace for you.
- To start receiving data, use the DSN (connection string) you've obtained on the previous step to configure OpenTelemetry for your programming language.
- Instrument your application with plugins for popular frameworks and libraries.
Have questions? Get help via Telegram, Slack, or start a discussion on GitHub.
Infrastructure monitoring
To monitor host (infrastructure) metrics, Redis, PostgreSQL, MySQL and many more, use OpenTelemetry Collector.
If you are using AWS, you can also send CloudWatch Metrics directly to Uptrace.
Logs monitoring
To monitor logs, you can use Vector and FluentBit integrations.
If you are using AWS, you can also send CloudWatch Logs directly to Uptrace.
DSN
Uptrace DSN (Data Source Name) is a connection string that is used to connect and send data to an Uptrace backend. It contains a backend address (host:port) and a secret token that grants access to a project.
For example, the DSN http://project1_secret_token@localhost:14318?grpc=14317 contains the following information:
httptells the client to disable TLS. Usehttpsto enable TLS.localhost:14317is an address of the Uptrace backend. The cloud version always uses theapi.uptrace.devaddress without a port.project1_secret_tokenis a secret token that is used for authentication.?grpc=14318is a GRPC port.
You can find your project DSN on the Project Settings page:
Resource attributes
Resource attributes are key-value pairs that provide metadata about the monitored entity, such as a service, process, or container. They help identify the resource and provide additional information that can be used to filter and group telemetry data.
| Attribute | Comment |
|---|---|
service.name | Logical name of the service. Uptrace provides an overview of all services. |
service.version | The version string of the service API or implementation. |
deployment.environment | Name of the deployment environment (aka deployment tier). Uptrace can group spans from different environments separately. |
host.name | Name of the host. Usually, resource detectors discover and set this attribute automatically. |
You can set those attributes by using the env resource detector and providing the OTEL_RESOURCE_ATTRIBUTES environment variable:
export OTEL_RESOURCE_ATTRIBUTES=service.name=myservice,service.version=1.0.0,deployment.environment=production
Or you can configure them during OpenTelemetry initialization:
// https://uptrace.dev/get/opentelemetry-go
import (
"github.com/uptrace/uptrace-go/uptrace"
"go.opentelemetry.io/otel/attribute"
)
uptrace.ConfigureOpentelemetry(
// copy your project DSN here or use UPTRACE_DSN env var
//uptrace.WithDSN("<FIXME>"),
uptrace.WithServiceName("myservice"),
uptrace.WithServiceVersion("v1.0.0"),
uptrace.WithResourceAttributes(
attribute.String("deployment.environment", "production"),
),
)