Collecting observability data like metrics, traces, and logs makes it much easier to identify bottlenecks and other performance problems in your .NET applications. When you need to troubleshoot a production incident, it’s especially important to be able to navigate all that data so you can find the source of the issue and enact a timely resolution.
When we started Rancher in 2014, our vision was to enable enterprise IT to procure and utilize computing resources (“cattle”) from any infrastructure provider. We were extremely lucky to be able to leverage wonderful technologies like Kubernetes which made computing resources consistent across all infrastructure providers.
Now this blog post is only going to cover the two largest cloud providers, Microsoft’s Azure and Amazon’s AWS and only focusing on Infrastructure as a Service (Azure VMs for Azure, and EC2 for AWS) offerings they both provide, but with a bit of a deep dive in to the way they both provide resilience.
What if we told you that most organizations are making simple AWS cost optimization mistakes that lead to surprising monthly cloud bills and unnecessary overspend? As an engineer, you’d probably be relieved to know that many of your organization’s AWS spending spikes are within your team’s control, given access to the right data.
Cost is a big reason many dev teams are transitioning to serverless. However, there are still some ways costs can creep up on you in serverless apps. The biggest culprit I’ve found in my own experience is the VPC resource. Because adding a VPC to a serverless stack is ridiculously easy in Stackery, I’ve sometimes gotten carried away. I’d deploy a stack with a VPC for testing, then quickly forget about it.
I fly a lot. Mercifully, not as much as your typical road warrior type, but enough where I’ve developed a routine on travel days. If it’s a good weather day, then I’ll hear the pilot announce, “We’ll be cruising at 33,000 ft. and expect clear skies all the way to our destination.” And if there’s lots of clouds? There’s auto-pilot, air traffic control and radar available to do some of the heavy lifting. That got me to thinking.
Gartner Catalyst Conference 2019 is consistently a great venue for learning, sharing, and connecting. OpsRamp was a silver sponsor at this year’s event and our seven-member contingent had a wonderful time meeting with industry thought leaders, demoing OpsRamp to senior IT executives, and having fun in the streets of San Diego. In this post, I will summarize the most interesting themes that stood out from the conference keynotes and sessions, as well as other key takeaways from the week.
Organizations of all sizes—but, in particular, the larger ones—view hybrid cloud infrastructures as the new normal. The Rightscale 2019 State of the Cloud Report from Flexera (registration required) surveyed close to 800 business, IT, and development professionals around the globe. They worked for both large and small organizations across a wide range of verticals.
k3sup: From zero to KUBECONFIG in < 1 min K3s is an open-source, lightweight Kubernetes distribution by Rancher that was introduced this year and has gained huge popularity. People not only like the concept behind it, but also the awesome work that the team has done to strip down the heavy Kubernetes distribution to a minimal level. Though k3s started as a POC project for local Kubernetes development, its development has led people to use it even at a production level.
If anyone asks: what is a patch? we have to abandon the semantic field of piracy and go to serious and technical things, so to speak.
