The latest News and Information on Cloud monitoring, security and related technologies.
Moving applications to a public cloud, no matter why you’re making that journey, is a high-stakes proposition. As an industry, we’re focused on rapidly moving forward to give our businesses the competitive edge they need. However, when it comes to cloud migration, we often fail to stop and ask some critical questions, and as a result we end up overspending and underperforming.
In February, we announced the general availability of InfluxDB on Google Cloud, as well as a rich set of integrations that allow you to use our time series data platform to monitor your Google Cloud services, store sensor data from Google IoT core, and send your time series data to Pub/Sub for analysis on Google AI Platform.
If you have discovered that your application demand changes over time, you’re probably wondering how you can continuously adjust your cloud capacity in accordance to application demand. If you use CloudFormation, then you’re in luck! This article walks through how you can update your template code to automatically implement infrastructure adjustments, periodically.
Now that you've learned your way around Log Analytics and Application Insights, let’s move on to discuss how you can set up alerting in Azure Monitor. Azure Monitor is the centralized console where you can create alerting around various resources in your subscription and also manage it.
Cloud applications don’t just run flawlessly by way of magic. Many things can go wrong, and rest assured some will go wrong at one point. For small teams, this can be cumbersome and take a toll at the development speed. A monitoring system will detect these issues on behalf of the development team, so that they can act accordingly. At Dashbird, we think there’s much more to it, though, than just detecting and alerting issues, especially for small teams of developers.
A good software design tool enables rapid visualization of application architectures, much like a virtual whiteboard. A great design tool validates service architectures, their communication flows and the infrastructure required to execute them—and builds a scaffold that can be seamlessly taken forward into development. Security is a vital component of that scaffolding, starting at the design stage and extending through the application lifecycle.
In the last post, we compared kiam and kube2iam head-to-head. While kube2iam was declared the winner of that comparison, I feel that the case for kiam too compelling, and the setup too complicated, to not share my experience setting it up in production.
