Operations | Monitoring | ITSM | DevOps | Cloud

IT structures across organizations are bound to get complicated one way or another. If you’ve been in business for at least a decade, chances are you’ve acquired a complex, layered system of technology that’s a hodge-podge of old and new. This complexity brings new challenges for infrastructure monitoring. It goes without saying that any enterprise needs effective IT infrastructure monitoring. But when technology is evolving at the pace it is, things can get difficult.

For quick, scalable, highly-available web services, few options compare to AWS Lambda. Just provide your code, add a little configuration, and you're done! In this article, Milap Neupane will introduce us to Lambda, show us how to get it working with Ruby and the Serverless Framework, and discuss reasons to use — or to not use! — Lambda in production.

In this article, we are going to see how we can integrate Google Cloud with Grafana. We will integrate Google Cloud SQL with Grafana and plot the metrics on Grafana. We will also look at how we can use Google Stackdriver as the data source in Grafana to expose the metrics of Google Cloud VM’s and platforms. To use Grafana immediately, we will be using Hosted Grafana by MetricFire.

Both Graphite and InfluxDB are time-series monitoring data platforms, both of which have high levels of adoption throughout many industries. Both of them are suitable for enterprise use, are scalable, and are stable. That being said, there are some benefits and drawbacks to each. While InfluxDB has many benefits, many developers still prefer Graphite due to its large community, stability, and reliability.

Using the cloud reduces on-premises infrastructure costs and related maintenance. Instead of deploying more servers, storage, and networking components to your own datacenter, you are now deploying these as cloud resources. Using the cloud is supposed to reduce infrastructure and maintenance costs. However, deploying cloud resources also risks over-commissioning, under-usage, and keeping resources running that are not always needed or, even worse, no longer in use.