Application crashes have a significant impact on customer experience, which can adversely affect a company’s reputation and revenue. Error and crash reporting is a unique feedback mechanism that provides true data about the quality of their product. Developer teams that create games, mobile applications, IoT, and other high-performance applications need rich insights into application health to quickly and continuously fix software errors with minimal impact.

We at Goliath Technologies are excited about our growing relationship with IGEL and our joint customers. Together we are improving and simplifying the end-to-end user experience as the marketplace adopts IGEL software defined endpoints. Our proactive end-user experience monitoring and troubleshooting platform works with IGEL, running on a Citrix or VMware Horizon delivery infrastructure, to automatically identify any events, conditions, or failure points that impact the workspace experience.

Our hosted metrics offering, Grafana Cloud, is billed based on usage; a common question we get is “How much will it cost to monitor N servers?” We charge $49/month for every 3,000 active series or 18,000 data points per minute (dpm), whichever is higher. To help you understand what that translates to in terms of how much storage you need, here’s a rough guide to estimating the size of your system.

A recent Gartner report states: “Organizations with a cross-discipline cloud strategy are more likely to find success in cloud initiatives and recognize the full benefits of cloud.” Advances in machine learning and AI have opened up avenues for forward-thinking enterprises to drive extensive automation using the latest cloud technologies.

Self Maintenance MP? isnt that Tao Yang’s management pack? you are along the right lines.. As Tao moves onto Azure he has handed the Self Maintenance MP to us to ensure it gets the love and attention deserves, and what better way to do that than with a new release! – its an awesome pack Good news for SCOM admins everywhere.

In this blog we are going to discuss how you can use Cookdown’s PowerShell MP to create SCOM tasks written in PowerShell and how you can visualise the output of your tasks in a much more efficient and user-readable format – using SquaredUp.

Monitoring systems gather and log a wide range of performance data on a diverse range of targets—from applications to user experience, networks, servers, and more. Usually, monitoring is conducted under runtime conditions, but synthetic monitoring can also be used to simulate loads and test the resilience of web services, for example.

There is a paradox at the heart of serverless. While it’s promoted as a very agile way to develop, a way to push your product as fast as possible to your customers, many development teams find it really difficult to work fast. Why does this happen and can we solve the issue? Let’s start with what makes serverless such a powerful paradigm. Serverless rests on three legs, each of which contributes to the agility that serverless is known for.

I’ve said this before, but I’m saying it again: observability is not a synonym for monitoring, and there are no three pillars. The pillars are bullshit.

Recently, we ran into a problem where a customer’s dashboard broke to such an extent that it hung on loading. This is a really rare problem and in this case was an instance where the customer had created a variable that referenced itself. Once the dashboard is broken in this way, it is impossible to reach a screen allowing you to remove that variable. This post is not about how it was broken, but about how we resolved the error.