Requirement #3: Resource Monitoring per TenantWith an APM solution capturing every single transaction and a business context analysis on top, we are able to group transactions by tenants. This allows us to exactly identify what resources and to what extent a particular tenant consumes, which further enables us to recognize if we’ve implemented our features efficiently and to detect if fair use policies are exceeded (fraud detection). In combination with dynaTrace smart baselining we automatically get notified if such situations occur.
For time cockpit, they built a dashboard to monitor overall database size, database size per tenant and CPU utilization per tenant. The dashboard shows right away that one customer is about to cross the red line and three are close to triggering a warning. The middle chart on the right shows that the pink customer consumes about one third of all CPU; the chart below illustrates time-based CPU utilization split by tenant. Thus, we become aware not only of general peak hours but furthermore of tenant specific peak hours.
[size=0.9em]Tenant-based resource usage: overall database size is fine, four tenants stick out, and one of them is close to violating capacity
Many more ratios are feasible: number of storage calls or Service Bus calls, if you have cost driving Azure resources in mind, but also any other resources can be monitored this way.
If you want to read more about the background of cost management in public clouds, I’d like to invite you to read this blog.
SummaryOrganizations make use of public cloud offerings because they want to focus on their revenue-generating application. And from there we already can draw the significance of Application Performance Management in public cloud environments. If we focus on our application, let’s also focus on its performance. Come back to read more about how a state-of-the-art APM solution can help you in public cloud environments. |