An alert that, when triggered, contains a step-by-step process that the on-call rotation can follow to triage, mitigate, and resolve the alert.
The practice of notifying an on-call developer (or developers) when one of a service’s key metrics has reached a critical or warning alert threshold.
Static or dynamic quantities that are set for each key metric signifying that the key metric in question is at a normal, warning, or critical level; reaching the threshold should trigger an actionable alert.
The third layer of a microservice ecosystem, containing self-service internal tools, the development environment, test, package, build, and release tools, the deployment pipeline, microservice-level logging, and microservice-level monitoring.
A well-defined client-side interface in each microservice that allows other services to interact with it programmatically by sending requests to static endpoints.
A high-level visual representation of the architecture of a microservice.
An organizational practice and process for evaluating, understanding, and improving the architecture of a microservice.
The term used to refer to servers owned, run, and maintained by the organization itself, as opposed to hardware rented from so-called cloud providers.
The second stage of the deployment pipeline containing ...