Real user monitoring (RUM) is a type of application performance monitoring that provides insights on how people interact with your app. With RUM, you can see what your users see by monitoring key elements of their experience within your application. There’s lots of industry buzz about observability, but for good reason. RUM is a critical part of digital experience monitoring because it’s incredibly valuable to understand user behavior and preferences.

Hello, and welcome to part two of the BugSnag Beginners Series! We will cover the error details page and how it can be used to maximize error debugging in your BugSnag Dashboard. We’ll start by going over how error details heading information is organized, followed by what different pivots mean, how the status box works, where to find diagnostic data, and lastly how to create custom filters using your error’s metadata.

Last month, TestGuild’s Joe Colantonio sat down with two of SmartBear’s product wizards to discuss the world of developer observability and upcoming trends. Eran Grabiner is co-founder of distributed tracing tool Aspecto, which was acquired by SmartBear earlier this year. Right now, he works as Director of Product Management for Aspecto spearheading observability projects. Justin Collier is a longtime member of the SmartBear team and currently serves as Senior Director of Product Management.

Apache Iceberg is transforming how organizations hanle data by solving key challenges in traditional data warehousing. It offers schema evolution without downtime, automated partitioning, ACID compliance, and time travel for historical data access. Its open table format separates storage and compute, enabling scalability, flexibility, and cost efficiency.

Software development requires a lot of things to be highly optimized due to the sheer number of parts and the interconnected nature of those parts. Making your service seamless, efficient, and scalable requires tooling that is itself seamless, efficient, and scalable. As organizations have moved to adopting microservices and distributed cloud-native solutions, being able to effectively scale resources and the systems which operate upon those resources has been made even more critical.

Software Testing is the most important step in the software development process. This process helps in validating and verifying that a software application is Bug-free, and the software is improved in terms of efficiency, accuracy and usability. Black Box Testing and White Box Testing are two most useful testing techniques for Software Testing. In this blog, we will be covering more about their definitions, advantages, disadvantages, their types, limitations and tools used for testing.

Ensuring secure access to applications and APIs is critical. As organizations increasingly adopt microservices architectures and cloud native solutions, the need for robust, fine-grained access control mechanisms becomes paramount. This is where the combination of Open Policy Agent (OPA) and Kong Gateway shines.

Service virtualization tools have become indispensable for organizations seeking to streamline their testing and development processes. These tools allow teams to simulate the behavior of critical software components, enabling more rapid development with overall cost reduction and improved collaborative outcomes. As demand mounts for service virtualization solutions, identifying the best tools to support this workflow in the software development lifecycle has never been so important.

Microservices are an approach to building applications that focuses on breaking down monolithic applications into independent, but loosely-connected “microservices.” ESBs and microservices are both architectural approaches for integrating applications, but they have different strengths and weaknesses. ESBs are better suited for integrating monolithic applications, while microservices are better suited for building scalable and resilient applications.

Let’s talk about stubbing and verifying – two critical tools that transformed how I approach testing. Early in my career, testing was often frustrating, slow, and full of surprises, most of them bad. I used to think testing meant running my app against real systems and crossing my fingers that everything worked. Spoiler: it rarely did. Here’s the thing: testing doesn’t have to be painful.