Modern customers demand that their applications are as seamless and error-free as possible. However, building such apps is a herculean task in itself. You need to constantly look out for incoming exceptions and warnings in your app in production. Effective error monitoring is key to resolving such issues before they are discovered by your users and cause a disruption in the quality of your services.
Monitoring cloud-native systems is hard. You’ve got highly distributed apps spanning tens and hundreds of nodes, services and instances. You’ve got additional layers and dimensions—not just bare metal and OS, but also node, pod, namespace, deployment version, Kubernetes’ control plane and more. To make things more interesting, any typical system these days uses many third-party frameworks, whether open source or cloud services.
AWS CloudFormation is a service that enables you to create and provision AWS infrastructure deployments predictably and repeatedly. This helps you leverage AWS products such as EC2 instances, Amazon Elastic Block Store, Amazon SNS, Elastic Load Balancing, and Auto Scaling to build highly reliable, highly scalable, cost-effective applications in the cloud – without worrying about creating and configuring the underlying AWS infrastructure.
HashiCorp Vault is an increasingly popular multi-cloud security tool that allows users to authenticate and access different clouds, systems, and endpoints, and centrally store, access, and deploy secrets. At Grafana Labs, we’re always looking for ways to make it easy for our community to get started monitoring important parts of their systems. So we’re happy to share some new integrations that will help our users get the most out of Grafana + Vault.
September and October were relatively quiet, so I thought I would write a single article for both months. While I'd normally try to write at least one useful article per month for OnlineOrNot's audience (as well as an update on how the business is going), I wrote no articles, and no code, actually. Instead, I packed up my life in Sydney, Australia, escaped lockdown, and relocated to France with my wife, and just enjoyed living for a while.
To give you enough notice to fix an issue before it escalates, we’re evolving our alerts and making them more proactive with Change and Crash Rate Alerts. So when your application experiences a change from the norm or a dip in crash-free sessions, Sentry will (smartly) alert you via Slack, Teams, PagerDuty, or old-fashioned email.
Here are the articles, videos, and tools that we’ve been excited about this October. We hope you enjoy these links, and we look forward to hearing what you’ve been reading in the comments or on the Interrupt Slack.
In the first part, I outlined some of the terms associated with the delivery of IoT. Next, let’s look at how this gets complex. You will need to read the state of each sensor (through their appropriate API and through their appropriate vendor-supplied hub), create logic to determine what actions must be taken when certain conditions are met, and then deliver these as a workflow to each responder, and confirm through data collected from sensors that the requested change was implemented.
In this blog post, I will be talking about label standard and best practices for Kubernetes security. This is a common area where I see organizations struggle to define the set of labels required to meet their security requirements. My advice is to always start with a hierarchical security design that is capable of achieving your enterprise security and compliance requirements, then define your label standard in alignment with your design.
