Learn how to analyze subscriber behavior using Kentik. In this post, we focus on the challenges and solutions of identifying and tracking the customers in an IP network while complying with regulations such as GDPR, show how Kentik Custom Dimensions and Data Explorer provide the analysis, and finally touch on how the associated APIs help automate and ease the entire process.

When we’re testing our apps, it's a big headache to simulate what the user goes through while steering clear of the more problematic parts of those processes. These parts, often external and beyond our control and responsibility, are usually not the focus of our testing. Think external services, third-party modules, or APIs. Relying on these unpredictable elements for our tests is a no-go. Nor do we want to rework our tests to check internal implementations just to dodge these issues.

In today's era dominated by digital connectivity, the pivotal role of Internet Service Providers (ISPs) in shaping our online experiences and facilitating business operations cannot be overstated. The quality of Internet services has emerged as a critical factor, directly impacting both individuals' daily activities and the operational efficiency of companies.

In today's digital-first landscape, maintaining the health and performance of your network is critical for the seamless operation of your business and its services. To that end, network observability has emerged as a key concept and discipline in ensuring the robustness and performance of networks. But what is network observability?

Google Workspace is a robust set of productivity applications with billions of users and millions of paying organizations. These include small mom-and-pop shops and the largest enterprises. Google provides the Google Reports API, “a RESTful API you can use to access information about the Google Workspace activities of your users.” This data is critical for establishing a solid security posture.

Table of contents As a golden rule of building a developer tool, you should always dog-food your own product. But, how does this work with a monitoring solution 🤔? Doesn’t it create a chicken and egg problem? Checkly uses multiple tools to monitor the platform, and tools from our competitors as well. However, we still dogfood our platform heavily. I believe this is mainly due to our engineers also liking the product and finding it quite easy to monitor their features.

Are you relying on outdated manual methods to monitor your network? Struggling to keep up with the increasing complexity of your IT infrastructure? Being constantly reactive to network problems instead of proactive in preventing them? If you answered yes to any of these questions, then you’re putting your business at risk. But don’t worry, there’s a way out — Remote Network Monitoring.