Operations | Monitoring | ITSM | DevOps | Cloud

If you’re running a production application, you need metrics. There are great products out there that allow you to gain visibility into how your application is performing, give some nice graphs, and charge you for it. In the Rails community, this is commonly achieved by using NewRelic and Skylight. But for some of us, we achieve visibility by using Prometheus and Grafana that we build and host ourselves.

In today’s software-driven economy, every organization faces an imperative to modernize the way they deliver software in order to adapt and enable the digital era — or perish. Digital transformation across industries is driving the need for IT to enable Cloud-Native applications. This has led enterprises to adopt Kubernetes as the most effective way to support cloud-native architectures and to modernize their applications and IT infrastructure.

Docker is a powerful tool for creating and deploying applications. It simplifies rolling out applications across multiple systems and is a useful tool for integrating new technologies. An application that runs using Docker will start up the same every time on every system. This means that if the application works on your local computer, it’ll work anywhere that supports Docker. That’s great news! It simplifies your development process and can be a powerful tool for continuous delivery.

I’m on the og-aws Slack group, one of the more active groups of AWS developers and cloud practitioners. A member of the channel, Samuell, asked a question about S3, Cloudfront, and new files, and I saw the perfect opportunity to help out, so I offered.

Last year we covered the top enterprise serverless use cases for AWS Lambda. To refresh our memory, according to the CNCF (Cloud Native Computing Foundation), most commonly AWS Lambda is used for REST APIs, multimedia/image processing, CRON jobs, and stream processing. Today I’d like to cover some more complex ways some of our enterprise customers use Lambdas.

No matter how carefully coded, reviewed, and tested your Ruby code is, odds are good that at some point you’ll cause a catastrophic failure to at least one system you’re responsible for. How do you prepare yourself? You need a Ruby debugger. In this post, I’ll cover the whole Ruby debugger process—from finding the issue to determining the root cause. Use these instructions for debugging a single Ruby file, a Rails app, or a gem.

If you work in tech, you’ve probably heard that “team culture” is the most important thing for a successful organization. Camaraderie, trust, passion… a good team should have all that. And it’s hard to deny that loving the team you work with will make you more successful, but how do we build that? There’s no AWS product called TeamFront and it’s not sold on Amazon. How can we take camaraderie from elusive to undeniable?

While Logz.io provides Kibana — the ELK Stack’s visualization tool — as part of its service, a lot of users have asked us to support Grafana. One of the leading open source visualization tools today, Grafana has some added value when compared to Kibana, especially around visualizing time-series data.

Each year we eagerly await the publication of the RightScale (now Flexera) State of the Cloud report to see which technologies and players are trending in the cloud ecosystem. In this year’s report (2019) one of the interesting takeaways is that in 2018 public cloud spending grew three times faster than private cloud and companies intend to spend almost 25% more on public cloud in 2019 than they did in 2018.

We all want to ship code on a daily basis. As developers, we want the faster feedback cycle that comes with continuous delivery, and we know it’s better for our team and product in the long run. So why do so many development teams still have such long release cycles? While long release cycles are tried and true and can be seen as more stable, teams sacrifice much more than faster feedback cycles.