The latest News and Information on DevOps, CI/CD, Automation and related technologies.
In Part 1 of this series, we discussed key metrics for monitoring Microsoft Azure SQL databases. We also looked at how your database resource and audit logs complement metrics to provide more insight into database performance, activity, and security. In this post, we’ll show you how to collect metrics and logs from your database instances and monitor them with Azure’s monitoring and reporting tools.
Microsoft Azure SQL Database is a platform-as-a-service (PaaS) database offering for modern cloud applications. It’s a fully managed service that runs on the latest version of the SQL Server database engine, enabling you to create highly available and performant database instances without needing to maintain hardware upgrades, patches, or backups.
We’ve all been there. After countless hours of development, you’re ready to take that app that works awesome on “localhost” live to production, but production services will only interface over https. Or maybe, your DNS is managed on Cycle, but some third-party app you want under the same domain requires a TLS certificate.
The global health crisis has accelerated the digital transformation within the financial services industry.
Unless you are one of the 1% of enterprises that have zero workloads running in the publice cloud, you need a cloud cost optimization tool. Yes, you do. And if you have workloads running in multiple public clouds—which somewhere in the neighborhood of 85% of enterprises do—you really need a cloud cost optimization tool. If I’m preaching to the choir, feel free to skip to the end of this article where you’ll find a link to try Virtana Optimize for free.
gRPC is a remote procedure call framework that has been widely adopted among cloud native applications. It is an attractive choice for engineers needing more capabilities than what REST APIs provide. However, observability and testing tools for gRPC are few and far between. Because of this, triaging or understanding application behavior is potentially time-consuming and overly burdensome.
