During PromCon, I gave a talk titled “The Future of Prometheus and its Ecosystem.” I want to share the key highlights with you.
The rapid pivot towards a remote workforce is forcing organizations to adopt a cloud-first approach faster than ever. We recently surveyed 500 IT decision-makers around the globe to ascertain their views on IT automation, cloud migration, and business continuity in the face of unexpected crises. The survey found that 87% of IT professionals agree that the current COVID-19 pandemic will cause organizations to accelerate their migration to the cloud.
If you’ve ever launched a startup, you know how hard it is to find funding. It’s a huge grind just to get from conception to execution without even worrying about profitability yet. But to attract an investor, you have to show consistent revenue growth to prove they will eventually see a return. Many, many startups fail before they reach a Series A. And the industry with the highest startup failure rate? The information industry, at 63%.
As a developer, getting metrics from your application onto a Prometheus graph can seem daunting. We’ll look at analyzing your service to find the most useful places to add metrics, how to add that instrumentation, getting it exposed and scraped, and then basic queries to use those metrics on graphs. Check out another article of mine for general reference on instrumenting, this one on Prometheus metrics, or this comparison on instrumentation alternatives.
In this tutorial, we will be using Heroku to deploy our Node.js application through CircleCI using Docker. We will set up Heroku Continuous Integration and Deployment (CI/CD) pipelines using Git as a single source of truth. Containerization allows developers to create and deploy applications faster with a wide range of other benefits like increased security, efficiency, agility to integrate with DevOps pipelines, portability, and scalability.
