Skip to content

Commit

Permalink
Fixed linting and the wrong key name for api token
Browse files Browse the repository at this point in the history
  • Loading branch information
Mr. GPT authored and Mr. GPT committed Jan 7, 2024
1 parent 8314092 commit 9aa583e
Showing 1 changed file with 13 additions and 8 deletions.
21 changes: 13 additions & 8 deletions .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,16 @@
# to be appended to the GRAFANA_OTLP_ENDPOINT in order to work.
# You get the following error
# Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-us-west-0.grafana.net, retrying in 1s.
# other iwse
GRAFANA_OTLP_USERNAME = '<Grafana Cloud Instance ID'
# use
# `echo -n "<your user id>:<your api key>" | base64 -w0`
GRAFANA_OTLP_USERNAME = 'Grafana User ID'
GRAFANA_OTLP_API_ENCODED_TOKEN = '<Grafana Cloud API Token>'
GRAFANA_OTLP_ENDPOINT = "<Grafana Cloud OTLP Gateway Endpoint for your Grafana Instance"
OTEL_PYTHON_LOG_CORRELATION = "true"
# otherwise
# We should switch to more standard OTEL_EXPORTER_OTLP_HEADERS
# For now use the Grafana API TOKEN as is.
# See https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/
GRAFANA_OTLP_API_TOKEN='<Grafana Cloud API Token>'
# we would use the standard OpenTelemetry environmental variables if not for the
# `/v1/traces`, `/v1/metrics`, `/v1/logs` that needs to added for
# tracing, metrics and logs endpoints
# See https://grafana.com/docs/opentelemetry/instrumentation/configuration/environment-variables/
# The standard is OTEL_EXPORTER_OTLP_ENDPOINT
GRAFANA_OTLP_ENDPOINT="<Grafana Cloud OTLP Gateway Endpoint for your Grafana Instance"
GRAFANA_OTLP_USERNAME='<Grafana Cloud Instance ID'
OTEL_PYTHON_LOG_CORRELATION="true"

0 comments on commit 9aa583e

Please sign in to comment.