Synthetic Transactions

Two types of Synthetic Transaction Metrics are collected on the Redis cluster – SLA metrics and local metrics.

SLA metrics are used by Instaclustr to provide a direct measure of the correct functioning of the system as seen by a client application. These metrics highlight if a client is unable to perform read/write operations on the Redis cluster. Rather than measuring if a specific node is unavailable, its purpose is to measure if read/writes are unavailable given the redundancy measures that Redis provides. Additionally, recording the latency of both read and write synthetic transactions will determine the quality-of-service of a Redis node.

On the other hand, for the purpose of troubleshooting, Local Metrics provide insights of individual master node performance. The synthetic read/write transactions are performed aiming each master node. These metrics help narrow down if a particular node is performing poorly.

  • Local Read Failed Operations: This metric shows number of failed read operations performed on the local node. Expected value: 0
    A graph of the number of failed local read operations on a Redis cluster.
  • Local Read Latency: This metric displays the average and maximum time taken in milliseconds by a client to read from its local node.
    Graphs displaying information on the latency of local reads on a Redis cluster.
  • Local Read Successful Operations:  This metric shows number of successful read operations performed on the local node. Every 20 seconds, 30 synthetic read transactions are performed on each node. Expected value: 30
    A graph of the number of successful local read operations on a Redis cluster.
  • Local Write Failed Operations: This metric shows number of failed write operations performed on the local node. Expected value: 0
    A graph of the number of failed local write operations on a Redis cluster.
  • Local Write Latency: This metric displays the average and maximum time taken in milliseconds by a client to write to its local node.
    Graphs displaying information on the latency of local writes on a Redis cluster.
  • Local Write Successful Operations:  This metric shows number of successful write operations performed on the local node. Every 20 seconds, 30 synthetic write transactions are performed on each node. Expected value: 30
    A graph of the number of successful local write operations on a Redis cluster.
  • SLA Read Failed Operations: This metric shows number of failed read operations performed on the cluster. Expected value: 0
    A graph of the number of failed SLA read operations on a Redis cluster.
  • SLA Read Latency: This metric displays the average and maximum time taken in milliseconds by a client to read from a random node in the cluster.
    Graphs displaying information on the latency of SLA reads on a Redis cluster.
  • SLA Read Successful Operations:  This metric shows number of successful read operations performed on the cluster. Every 20 seconds, 30 synthetic read transactions are performed on each node. Expected value: 30
    A graph of the number of successful SLA read operations on a Redis cluster.
  • SLA Write Failed Operations: This metric shows number of failed write operations performed on the cluster. Expected value: 0
    A graph of the number of failed SLA writes on a Redis cluster.
  • SLA Write Latency: This metric displays the average and maximum time taken in milliseconds by a client to write to a random master node in the cluster.
    Graphs displaying information on the latency of SLA writes on a Redis cluster.
  • SLA Write Successful Operations:  This metric shows number of successful write operations performed on the cluster. Every 20 seconds, 30 synthetic write transactions are performed on each node. Expected value: 30
    A graph of the number of successful SLA writes on a Redis cluster.

By Instaclustr Support
Need Support?
Experiencing difficulties on the website or console?
Already have an account?
Need help with your cluster?
Contact Support
Why sign up?
To experience the ease of creating and managing clusters via the Instaclustr Console
Spin up a cluster in minutes