Recently, a colleague of mine joked that she manages a marketing team of three: Claire, Mark, and Sally. The punchline is that she’s referring to Clearbit, Marketo, and Salesforce. She felt that way because they each have their own role with unique insights and jobs, and her team shares information with everyone else the same way she does through chat.
New applications and workloads are constantly being added to Kubernetes clusters. Those same apps need to securely communicate with resources outside the cluster behind a firewall or other control point. Firewalls require a consistent IP, but routable IPs are a limited resource that can be quickly depleted if applied to every service.
My name is Kat Cosgrove, and I’m a Developer Advocate at JFrog. Before that, I was an engineer on JFrog’s IoT team. Our goal is to bring DevOps to the edge, because it shouldn’t be as difficult to update these kinds of devices as it currently is. In pursuit of this goal, we found a lot of interesting solutions that we could bring into a CI/CD pipeline for embedded Linux devices, and eventually built a rather flashy proof of concept that put several of these solutions on display.
The Business Process module is used to visualise all the objects in Icinga in a hierarchical format. This way, you can visualise your data in a way that fits its application! You can create custom process-based dashboards and trigger notifications at process or sub-process level. You can also have a quick top-level view for thousands of components on a single screen.
One of the first things incident managers do when they get an alert page from Zenduty is to check the “Context” tab of the incident. Incident context is extremely critical to get a first responder’s view of what happened and what could possibly have caused it. Context tells you what happened before an incident. In the case of 40–50% of all incidents, Zenduty’s incident context can tell you within 5–10 seconds, what could be the cause of an incident.
Exciting times ahead. With the Jamstack gaining momentum, the landscape around it is offering more and more tools to streamline developer workflows and free up time for actual development. A cutting edge solution in this interesting space is Vercel, formerly known as ZEIT. In this blog post we will get a taste of Vercel's capabilities by using it to deploy and preview a sample Gatsby blog - and while we're at it, we will of course take the chance to kick off some checks automatically from Checkly.
This post is the first in a three-part series on how to effectively monitor the hosts and systems in your ecosystem, and we're starting with the one you use most: your personal computer. Metrics are a key part of observability, providing insight into the usage of your systems, allowing you to optimize for efficiency and plan for growth. Let's take a look at the different metrics you should be monitoring.
DevOps pipelines enable teams to implement continuous software development processes, often by using automation and collaboration tooling. The overall goal is to quickly release software products, updates, and fixes. To ensure a DevOps pipeline works well, teams add management and monitoring tooling to the pipeline. This includes incident alert management, which supports the team’s efforts in monitoring the security of various software and environment components.
Software Engineering is hard. As time has progressed, the number of languages, frameworks and packages available has grown to the point where it’s rare nowadays to find a project that is developed entirely in a single language or within a single ecosystem. A typical project uses the best languages and frameworks for the job, and these frequently differ depending on what part of the project is being developed.
