Docker
Alternatively, you can deploy the docker container for the Asserts Collector asserts/otel-collector:latest-release-all-exporters
and configure it to as per your requirements. The following are the environment variables that can be used to configure the collector
TRACE_STORE
The trace store backend. Allowed values are
AWS-XRAY Specify this value for AWS X-Ray
GOOGLE-CLOUDTRACE Specify this value for Google CloudTrace.
GCP_PROJECT_NAME The GCP Project name
Note on Authentication: Please note that Google credentials need to be passed as a json file. The path of this json can be configured through an environment variable. See Google documentation for more details. You will have to set this environment variable and mount the credentials file while launching the container
OTLP-HTTP Specify this value for any OTLP compatible backend with traces sent over HTTP
OTLP Specify this value for any OTLP compatible backend with traces sent over gRPC. You can choose this value when sending traces to Grafana Tempo.
ASSERTS_TENANT
Set this to the Asserts tenant name. In self-hosted mode, set this to bootstrap
ASSERTS_ENV
Asserts has first class support for segregating all data by environments. Set this value to the environment in which the collector is being deployed.
ASSERTS_SITE
In production environments, applications can be deployed in multiple regions. The collector should be collocated with the source of the telemetry. The region can be specified through this environment variable.
ASSERTS_SERVER_API_ENDPOINT
The Asserts collector connects to the Asserts server to retrieve configuration information.
ASSERTS_SERVER_USERNAME
ASSERTS_SERVER_PASSWORD
LOG_LEVEL
Last updated