Coté

Self-help/improvement type-stuff, mostly. Original source: Books To Base Your Life on (The Reading List)

If the response takes too long to get to your phone, the system might as well be “unavailable”: ‘If a page takes too long to load a user will consider it to be unavailable. I realized after the fact the nuances of this were not considered in the phrasing of one of our questions. We asked “What service level indicators are most important for your services?” Three of the options were end-user response time, latency, and availability.

If the response takes too long to get to your phone, the system might as well be “unavailable”: ‘If a page takes too long to load a user will consider it to be unavailable. I realized after the fact the nuances of this were not considered in the phrasing of one of our questions. We asked “What service level indicators are most important for your services?” Three of the options were end-user response time, latency, and availability.

If the response takes too long to get to your phone, the system might as well be “unavailable”: ‘If a page takes too long to load a user will consider it to be unavailable. I realized after the fact the nuances of this were not considered in the phrasing of one of our questions. We asked “What service level indicators are most important for your services?” Three of the options were end-user response time, latency, and availability.

Lists out how to get the metrics from various systems and software. Original source: Monitoring SRE’s Golden Signals

Lists out how to get the metrics from various systems and software. Original source: Monitoring SRE’s Golden Signals

Lists out how to get the metrics from various systems and software. Original source: Monitoring SRE’s Golden Signals

[Summary from the post of metrics to use:] Rate — Request rate, in requests/sec Errors — Error rate, in errors/sec Latency — Response time, including queue/wait time, in milliseconds. Saturation — How overloaded something is, which is related to utilization but more directly measured by things like queue depth (or sometimes concurrency). As a queue measurement, this becomes non-zero when you are saturated, often not much before. Usually a counter. Utilization — How busy the resource or system is.

[Summary from the post of metrics to use:] Rate — Request rate, in requests/sec Errors — Error rate, in errors/sec Latency — Response time, including queue/wait time, in milliseconds. Saturation — How overloaded something is, which is related to utilization but more directly measured by things like queue depth (or sometimes concurrency). As a queue measurement, this becomes non-zero when you are saturated, often not much before. Usually a counter. Utilization — How busy the resource or system is.

[Summary from the post of metrics to use:] Rate — Request rate, in requests/sec Errors — Error rate, in errors/sec Latency — Response time, including queue/wait time, in milliseconds. Saturation — How overloaded something is, which is related to utilization but more directly measured by things like queue depth (or sometimes concurrency). As a queue measurement, this becomes non-zero when you are saturated, often not much before. Usually a counter. Utilization — How busy the resource or system is.