I came across several answers relating to temporal servermetrics. I am new to temporal and would like to understand the following:
- When is service_latency, service_error_with_type, persistence_errors and persistence_latency metric useful?
- what does task_schedule_to_start_latency do?
3.Difference between an sync match and async match. what is an async match latency ?
- Difference between workflow lock contention and shard Lock contention. what does cache_latency_bucket do?
Are there any other important metrics that need to be monitored from a cluster level? Please mention if there any document that tells what every server metric does.
Thank you @tihomir for your quick response. That helps.
Can you tell me the unit for these metrics ? Service_requests, service_error_with_type and persistence_requests.
Is there any threshold that can be set for persistence_latency and service_latency?
persistence_requests are all counters
persistence_latency will depend on your db capacity and workload, typically should be in low hundreds of ms. Note that unprovisioned workers can also add extra pressure on db.
service_latency might also depend on how optimized your workers are as well as use case (for example burst use cases)
Thanks for clearing up again @tihomir.