Managing the infrastructure monitoring system in a large-scale IT environment can be incredibly tedious. I’d be willing to bet that you’ve run into at least one of these issues or something similar. APIs exist because user interfaces can’t do everything, and we’re all very happy that they do! Zenoss Cloud supports two APIs: a JSON API for bulk administration and a streaming data ingest API to allow a wide variety of devices to publish data directly.

We’ve changed Transaction steps and Multi-step API Monitoring steps to Transaction credits and Multi-step API Monitoring credits. In short: Steps are used to group your actions in your monitor definitions, and credits are used to buy Transaction or Multi-Step API monitors. Let’s explain that in more detail.

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.

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.

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.

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.

Ok, not completely true. I also use Stripe, Github, AWS, Heroku, Ghost, AppOptics, Intercom and Mailchimp. And some bookkeeping and tax tools. Don't forget the code editors! But! When I plan my day, I spend most of my time in Trello and Apple's stock Reminders app. I also use Numbers once a week or so. This post is turning out to be click bait. Read on, it's really not. In former jobs I went through probably every project management and productivity tool out there.

Recently I pushed a long overdue feature for Checkly: SSL for customers' public dashboards. This was kinda, sort of, totally missing when I launched and many customers asked for it. Setting up free SSL turned out to be fairly smooth because of Most principles explained here are totally transferable to whatever stack you are using. There are some pretty important gotcha's though, so let's dive in. Customers of Checkly can create public dashboards and host them on a custom domain.

Pulling in data exposed via API is not one of the most common use cases for ELK Stack users but it is definitely one I’ve come across in the past. Developers wrapping their database services with REST API, for example, might be interested in analyzing this data for business intelligence purposes. Whatever the reason, the ELK Stack offers some easy ways to integrate with this API. One of these methods is the Logstash HTTP poller input plugin.