I’ve tackled this question before: how much should my observability stack cost? While the things in that post are true now as ever, I did end on one somewhat vague conclusion. When it came to figuring out exactly what you need in your stack by drawing a straight line from the business case to the money you spend, my conclusion was that “it depends.” That’s how we approached pricing at Honeycomb: it depends on your needs, so we should give you many different options.

Logging is an essential method to understanding what’s happening in your environment. Logs help developers and system administrators understand where and when things have gone wrong. Ideally, logs on their own would suffice as indicators of what’s happening. However, there’s far too many log messages being produced in today’s world and most don’t contain the information we actually need.

About 90% of all Lambda functions monitored by Dashbird on AWS Lambda are running Nodejs and Python runtimes. Is this purely a reflection of the general popularity of these programming languages?

Most business owners nowadays are not even aware if their website is reaching the potential customers or not. And believe us when we say this, not having an effective outreach is the same as not having a website. In today’s constantly evolving internet spectrum, if you own a website and intend to drive business through it, Search Engine Optimization (SEO) is imperative for you.

A good application monitoring solution will provide you with the visual representation of the performance, growth, and usage of your AJAX applications. These metrics, along with others, are the critical metrics that need to be checked to ensure no interruptions occurs. Monitoring your applications ensures that your application is delivering you the results it was actually designed for. Below are the few reasons to have your application monitored.

WebSockets have been around for over a decade now, but the real-time web existed long before they came. This preceding ‘real-time’ web was typically slower and hard to achieve. It was attained by hacking available web technologies that were not primarily built for real-time applications. There was no solution with TCP/IP socket-style capabilities in a web environment that could address all concerns associated with operating in a web environment.

Some of our users have received reports about their AddTrust External CA Root or USERTrust RSA Certification Authority certificate. The problem occurs because the remote server sends a root certificate in the chain that will expire in less than 14 days. Here are the steps to verify this and a few tips on how to resolve it.

Remote workforces are becoming the new normal. What could be achieved earlier with a simple visit to your colleague’s desk will now require you to communicate flawlessly across miles. ITSM tools that were earlier used only when systems had issues are now being used to make delivery of different business services easier. Quite naturally, not all organizations are prepared for this ‘new normal’.

What is Stuck Thread? A Stuck Thread is a thread which is processing a request for more than maximum time that you configured in admin console. By Default, the WebLogic server comes with 600 secs. If some thread doesn’t return in 600 secs, It gets a flag ‘stuck thread’. How to deal with Stuck Thread? Take thread dumps instantly. Open thread dumps in visualVM. Analyze dashboard from WebLogic console (managed server > monitoring > threads).

We’re excited to announce our support for GitHub Actions with our new Rollbar Deploy GitHub Action. Teams using GitHub Actions for building their CI/CD pipeline can now easily send deploy information to Rollbar and respond to any new errors quickly.