This is the ninth part of our 12-day Advent of Monitoring series. In this series, Checkly's engineers will share practical monitoring tips from their own experience. As a Checkly user, you’ve always had access to our two core check types: API and browser checks. API Checks are much cheaper, and therefore only run a curl-like request against the endpoint of your choice.
In today’s business landscape, efficient management of digital resources is paramount, especially when it comes to collaborative platforms like SharePoint Online. As organizations increasingly rely on SharePoint for document management, communication, and collaboration, the costs associated with its usage can escalate quickly. This is where strategic cost management becomes essential.
This recurring blog will look at specific ITOM technologies within the OpsRamp solution and general ITOM challenges. Got an idea for this blog or want to learn more about ITOM at OpsRamp?
A powerful open-source container orchestration system, Kubernetes automates the deployment, scaling, and management of containerized applications. It’s a popular choice in the industry these days. Automating tasks like load balancing and rolling updates leads to faster deployments, improved fault tolerance, and better resource utilization, the hallmarks of a seamless and reliable software development lifecycle.
Are Git tasks like rebasing your Git branch or cherry-picking commits causing you headaches? Sometimes, without the right know-how, version control can turn seemingly simple tasks into daunting challenges. And when you’re collaborating among a team, the stakes are even higher. In addition to potentially losing your own code, you can compromise the work of other developers.
I have spoken with many prospects and partners over the years and one of the more frequent questions I am asked is: “How do you build Custom Monitoring”. This is not an easy question to answer as there are so many variables at play, including: what type of device are you trying to monitor, what metrics are you looking for, what thresholds should trigger a warning or failure, etc.
If you have large(r) customers, there is a point where they ask you for service-level agreements, or short SLAs. These are customer contracts defining different aspects of your service and what you guarantee for them. One common agreement is around availability, or, colloquially speaking, uptime. Your contract might state, and I am not a lawyer, that you guarantee that your service (or core parts of it) is available 99.99% of the time of a given period, mostly per month, quarter, or year.
