Operations | Monitoring | ITSM | DevOps | Cloud

In a recent post on customer feedback I mentioned being a recent convert to chat widget-driven tools. I thought they sucked, but I was wrong. Since then, I actually switched from Drift to Intercom because Intercom's focus — support & communication — matched my business better than Drift's heavy sales focus. To get the most out of Intercom, you need to integrate it with your app. This means instrumenting some code and tweaking some bits of your app's navigation.

If you’re not familiar with APIs, let’s run through a quick primer. API stands for application programming interface and refers to a set of tools and protocols that makes it possible to easily and efficiently access a software or hardware system from the outside.

We’re happy to tell you that we’ve released a brand new mobile app for Android and iOS! We released the first version a few months ago on Android, and we’ve since added some great new features. The new version is ready for you in either the Google Play Store or Apple’s App Store. The perfect addition to your website monitoring regime.

AWS API Gateway is a completely managed service that makes developers’ job much easier by allowing them to publish, create, monitor, maintain, and secure APIs at any scale. In today’s article, we’ll talk more about API Gateway What is it, why is it so important, as well as how it can help us with?

Ben Kehoe wrote a post about AWS API Gateway to Lambda integration: How you should — and should not — use API Gateway proxy integration with Lambda. In his post, Ben gave a few reasons why he believes using API Gateway Proxy Integration is an anti-pattern. Ben does a great job summarizing how the integration works. He writes: The pattern that I am recommending against is the “API Gateway proxy integration” as shown in the API Gateway documentation here.

There used to be a distinct, technical separation between terms such as AI and machine learning (ML) – but only while these technologies remained largely theoretical. As soon as they became practical in the real world, and then commodifiable into products, the marketers stepped in. Widespread overuse of the terms AI/ML in marketing have managed to thoroughly confuse the meanings of these words.

If you happen to be running multiple clusters, each with a large number of services, you’ll find that it’s rather impractical to use static alerts, such as “number of pods < X” or “ingress requests > Y”, or to simply measure the number of HTTP errors. Values fluctuate for every region, data center, cluster, etc. It’s difficult to manually adjust alerts and, when not done properly, you either get way too many false-positives or you could miss a key event.

Open source is one of the key drivers of DevOps. The need for flexibility, speed, and cost-efficiency, is pushing organizations to embrace an open source-first approach when designing and implementing the DevOps lifecycle. Monitoring — the process of gathering telemetry data on the operation of an IT environment to gauge performance and troubleshoot issues — is a perfect example of how open source acts as both a driver and enabler of DevOps methodologies.

You can use our API to trigger an on demand run of both the uptime check and the broken links checker. If you add this to, say, your deploy script, you can have near-instant validation that your deploy succeeded and didn't break any links & pages. Our API allows you to trigger an on demand run for every check we do. But, it's an API - so it requires a set of IDs. First, let's find the different checks your site has.