Operations | Monitoring | ITSM | DevOps | Cloud

So you’ve just been tasked with creating a Terraform Provider (or maybe upgrading an existing one). As you do your research to prepare for the project, you slowly begin to realize, “well this looks like I’ll just be developing a Terraform specific wrapper for a client of my API.” It’s not particularly difficult, but it seems tedious. Is there a better way to build this? Maybe something that can be modular and automated? A way that’s actually stimulating to implement?

BigPanda offers a diverse set of APIs to enterprises looking to move faster and scale incident response workflows seamlessly. APIs are core to automating repeated incident response workflows that enable IT Ops to keep up with the pace of change and innovation agile teams need to thrive. In Q4 of 2021, BigPanda announced the general availability of new self-service APIs including an updated Incidents API.

The explosion of talent available for remote work (and the widespread acceptance of remote first employment) allows for global collaboration on an unprecedented scale.

We’ve already outlined why API performance matters and what aspects of APIs to test, but what is the difference between API testing and monitoring? As with most things, context matters. The use cases for testing and monitoring are different because the objectives are different. The ultimate goal is to verify that your APIs are functioning properly, but staging environments vary significantly from production environments.

Digital businesses are making a radical change in the way they build and deliver software. Gone are the days of apps that rely solely on in-house tools. Rather, today’s apps are increasingly dependent on external APIs and third-party app providers (which, in turn, are reliant on other APIs and apps). While this type of modularity allows for product flexibility and rapid development, it can be difficult to address any issues that arise.

gRPC is an open source Remote Procedure Call (RPC) framework developed by Google and released in 2016. Although gRPC is still relatively new, large organizations are adopting it in increasing numbers to build APIs to connect complex microservice meshes that use disparate languages and frameworks. gRPC-based APIs can process requests up to seven times faster than REST APIs, and they also allow customers to easily implement SSL authentication, load balancing, and tracing via plug-in libraries.

In this load test tutorial, you’ll learn how to use Postman for small-scale API testing. You’ll also learn about some shortcomings and challenges of the framework that can be solved by using a tool like Speedscale. Because HTTP services don’t have a graphical user interface, you’re forced to test web APIs by simulating requests from a known client so that you can control the traffic data.

We offer an API that provides direct access to features the platform offer, with each feature providing a set of endpoints to perform operations on resources associated with your account. The StatusCake control panel offers plenty of useful visualisations and alerting systems so you can be in touch with your data, but sometimes we may have use-cases where we would rather leverage the API so in this blog post we’re going to see how we can make use of these endpoints using C#.