The primary intent of having a naming convention for Azure resources is to be able to identify essential information about a resource, for example: * related
In the first part of this series, I wrote about running Ghost on Azure Web App for Containers. Here we will explore some security improvements to the original deployment configuration, as I promised last time.
Access management in Azure is a broad and complex topic consisting of many interconnected parts, including Azure Active Directory, the Role-based Access Control (RBAC) model, resource permissions, service-specific access configurations, and so on.
Despite the common misconception, monitoring in a DevOps-aligned organization is not about “Hey, let’s use Prometheus, ELK, Grafana or whatever else and output nice dashboards on big wall-mounted screens!” Moreover, monitoring is not about tools and underlying technologies.
How do you understand uptime / SLA? Do you know what it means for your system? How much are you willing to pay? How much money will you lose each hour your system is down? What is a reasonable uptime? Let's try to answer these questions.