Skip to main content
Skip table of contents

Grafana SLA, AWHT Pipeline

Introduction

Grafana SLA, AWHT pipeline is responsible for calculating the SLA and AWHT, queue wise from the agent_task table

Configurations

Following are the configurations which are provided in transflux/config/graphana_queries.yaml

CODE
pipelines:
  AWHT:
    queries:
      - avg_wait_handle_time_AWHT
  SLA:
    queries:
      - graphana_SLA

target:
  type: "mysql"
  db_url: "mysql+pymysql://monty:Expertflow%23143@192.168.2.18:3306/cimfedev"
  # db_url: "mssql+pyodbc://sa:Expertflow464@192.168.1.77:1433/testing_ali?driver=ODBC+Driver+17+for+SQL+Server"
  enable_ssl: false  # Enable or disable SSL connections
  ssl_ca: "/transflux/certificates/mysql_certs/ca.pem"
  ssl_cert: "/transflux/certificates/mysql_certs/client-cert.pem"
  ssl_key: "/transflux/certificates/mysql_certs/client-key.pem"

schedule_interval: "*/60 * * * *"
time_offset: "0"
interval_minutes: 60
start_date: "2025-05-19T00:00:00+00:00"  ## Set to current datetime (UTC)
catchup: true

Edit the following as per dedicated environment

  • type: Use “mysql” or “mssql” as per selected database

  • db_url: Use the connection string according to the selected database type, the format is given below

    • For MYSQL

      CODE
      mysql+pymysql://<your-db-username>:<password>@<host>:<port>/<mysql-db-name>
    • For MSSQL

      CODE
      mssql+pyodbc://<your-db-username>:<password>@<host>:<port>/<mssql-db-name>?driver=ODBC+Driver+17+for+SQL+Server"
  • start_date: From when the pipeline will start running and compete it schedules. Set it to current date time

The schedule_interval, time_offset and interval_minutes are adjusted to run the pipeline after every one hour

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.