PostgreSQL is a great general purpose. Jaeger-PostgreSQL is intended to allow jaeger to use postgresql as its backing storage solution for projects with low traffic.

Installation is done through the use of a helm chart.

helm install myrelease oci:https://ghcr.io/robbert229/jaeger-postgresql/charts/jaeger-postgresql \
    --version v1.7.0 \
    --set database.url='postgresql:https://postgres:password@database:5432/jaeger'

# database connection options
database:
    # url to the database
    url: "postgresql:https://postgres:password@database:5432/jaeger" 
    
    # the maximum number of database connections 
    maxConns: 10 

# configuration options for the cleaner
cleaner:
    # when true the cleaner will ensure that spans older than a set age will
    # be deleted.
    enabled: true

    # go duration formatted duration indicating the maximum age of a span 
    # before the cleaner removes it.
    maxSpanAge: "24h" 

The Helm chart will deploy a service with the same name as the helm release. The configuration of Jaeger to use jaeger-postgresql depends on how you deployed jaeger. Adding the following argument to the jaeger's services, along with the acompanying environment variables to your jaeger services will configure jaeger to use Jaeger-PostgresQL for storage

--grpc-storage.server=jaeger-postgresql:12345

SPAN_STORAGE_TYPE="grpc-plugin"

The official jaeger documentation is the best place to look for detailed instructions on using a external storage plugin. https://www.jaegertracing.io/docs/1.55/deployment/#storage-plugin

John Rowley 💻

Jozef Slezak 💻

This project started out as a simple fork of Jozef Slezak's plugin of the same name, but was eventually completely rewritten.