In business, it’s important to ensure that you are getting the most out of the tools that you are paying for. If it’s a monitoring service, the data you collect should give you actions to help improve incident management by identifying the root cause of user issues faster. Assessing the return on investment (ROI) for all of the tools you use in your IT department is an essential step for improved efficiency and adoption of applications.
I am a challenger. It’s in my DNA somewhere I am sure. To find limits. Evaluate them. Develop an attack angle. Push beyond. Repeat. This is largely due to my hobby of cycling, which I had no idea would further develop my challenger habits when I took it up a handful of years ago. In cycling, it’s easy to find targets for goals. Sprint to the next intersection. Ride up a climb. Complete a 100-mile century. For me, it came in the form of a particular one-day cycling race covering 205 miles.
Last week, Catchpoint was one of the sponsors of Splunk’s half-day DevOps & Observability Best Practices event. It was a jampacked conference that examined what observability is, its key drivers, and how observability and monitoring exist “like two peas in a pod”, perfect compliments to one another in enabling enterprise to better understand overall systems behavior and health.
It is undeniable that today we really live in cloud… of virtual servers. It is so because the vast majority of services and applications “rely” on them: any survey shows, outright, that users use them very frequently (banks, universities, e-commerce, etc.). But, how is virtual server monitoring done? Pandora FMS has done its homework and today I will explain how.
We are really excited to announce that you can now use Playwright in your browser checks. If you didn't know yet, Playwright is Microsoft's headless browser library. It's very similar to Puppeteer. In fact, it was built by the original creators of Puppeteer and has mostly the same features and a remarkably similar API. This was in our public roadmap and cooking for some time now and we're glad to have it out the door!
As many recent studies show (like this one from Mckinsey) , self-service in B2B products is a growing trend. Today’s enterprise users expect the same seamless and simple experience they’ve learned to love as consumers. This works well for many simple tasks. But when it comes to more complex actions that require working with ‘under the hood’ technical features, things haven’t changed much since the early days of enterprise technology.
Now that you’ve chosen to go the serverless route, which vendor option should you go for? That’s one of the major questions that anybody asks themselves when they make the switch. Should you choose Amazon Web Services (AWS), which is a mature service that will serve you well, or should you go with e Google’s younger Firebase? Before the comparison of AWS vs Firebase, we should understand what serverless really means. This one server can be responsible for several different functions.
The world became a different place post Covid-19, and how we work, communicate and collaborate has been redefined—possibly forever. When “shelter in place” hit the entire world, we were not sure how we’d be able to execute our projects, customer commitments, and day-to-day operations. OpsRamp, an ITOM provider, has a distributed team across the U.S. and India for development and operations, and most of our engineers rarely worked from home.