GreptimeDB

Getting Started

Configuring Destination Fields

Supported Signals:

❌ Traces ✅ Metrics ❌ Logs ❌ Profiles

GREPTIME_ENDPOINT string : OTLP HTTP Endpoint.
- This field is required
- Example: https://<unique_id>.<aws_region>.aws.greptime.cloud
GREPTIME_DB_NAME string : Database Name.
- This field is required
GREPTIME_BASIC_USERNAME string : Basic Auth Username. The left part (from ”:”) of the Basic Auth Token.
- This field is required
GREPTIME_BASIC_PASSWORD string : Basic Auth Password. The right part (from ”:”) of the Basic Auth Token.
- This field is required

Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:

Using the UI

Use the Odigos CLI to access the UI

odigos ui

Click on Add Destination, select GreptimeDB and follow the on-screen instructions

Using Kubernetes manifests

Save the YAML below to a file (e.g. greptime.yaml)

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: greptime-example
  namespace: odigos-system
spec:
  data:
    GREPTIME_BASIC_USERNAME: <Basic Auth Username>
    GREPTIME_DB_NAME: <Database Name>
    GREPTIME_ENDPOINT: <OTLP HTTP Endpoint>
  destinationName: greptime
  secretRef:
    name: greptime-secret
  signals:
  - METRICS
  type: greptime

---

apiVersion: v1
data:
  GREPTIME_BASIC_PASSWORD: <Base64 Basic Auth Password>
kind: Secret
metadata:
  name: greptime-secret
  namespace: odigos-system
type: Opaque

Apply the YAML using kubectl

kubectl apply -f greptime.yaml

Getting Started

Instrumentations

Odigos Pipeline

Destinations

Concepts

Contribution Guidelines

Getting Started

Configuring Destination Fields

Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

​Getting Started

​Configuring Destination Fields

​Adding Destination to Odigos

Using the UI

Using Kubernetes manifests

Getting Started

Configuring Destination Fields

Adding Destination to Odigos