Typesense By Collection

Typesense traffic and latency per collection and action, and document counts per collection. Uses typesense-prometheus-exporter 1.x.

Typesense By Collection screenshot 1

Typesense traffic broken down by collection: requests per second and latency for each method, collection and action (search, import, documents, ...), plus document counts per collection, so you can see which collections carry the load.

Part of a set of four Typesense dashboards for typesense-prometheus-exporter, an open-source Prometheus exporter for Typesense: Cluster Overview, Stats, Metrics and By Collection. The dashboards link to each other from the top bar.

Requirements

Setup

  1. Run the exporter next to each Typesense node, or one exporter for the whole cluster with /probe?target=typesense-1.internal:8108:

    docker run -d -p 8888:8888 \
      -e TYPESENSE_HOST=typesense-1.internal \
      -e TYPESENSE_API_KEY_FILE=/run/secrets/typesense/api-key \
      imatefx/typesense-prometheus-exporter:latest
    
  2. Add it to Prometheus:

    scrape_configs:
      - job_name: typesense-exporter
        scrape_timeout: 10s
        static_configs:
          - targets: [exporter-1.internal:8888]
    
  3. Import this dashboard and pick your Prometheus data source. Use the host and collection variables to filter nodes and collections.

Documentation

Revisions
RevisionDescriptionCreated

Get this dashboard

Import the dashboard template

or

Download JSON

Datasource
Dependencies