We all want lightning-fast websites and applications, but how do we prioritize our efforts in order to have the biggest impact on performance? We interviewed our own front-end team so we could share some best practices we use every day to improve and maintain the performance of Raygun.

Redis, which stands for Remote Dictionary Server, is an open source, in-memory data structure store that’s used as a database, memory cache, and message broker. It stores data entirely in memory in the form of key-value pairs. This gives it an edge over all other databases, as it eliminates the need to access data from the disk. It also makes Redis one of the fastest NoSQL databases, where data is accessed in microseconds because there are no seek time delays.

Many Grafana users export images of their dashboard panels. This feature powers the ability to receive alerts with a rendered image of the panel attached, which is valuable for quickly spotting if something is about to go sideways in production. Since Grafana v2.0, when support for server-side rendering of dashboard panels as images was introduced, PhantomJS has served as the built-in image renderer that enables this feature.

AWS security is an ongoing battle that you must address during every release, every change, and every CVE. When you’re first launching your production application, it’s impossible to check all the boxes; you simply don’t have the time. Until your application gets more adoption, you only have the time to do the bare essentials of security.

A few weeks ago, we announced that Sysdig is offering fully compatible Prometheus monitoring at scale for our customers, as well as a new website called PromCat.io hosting a curated repository of Prometheus exporters, dashboards and alerts. This got me thinking about how we were actually able to implement the changes necessary to offer this in our platform.

In an always-on world, companies look to systems and processes to keep their services up and running at all times. The most important part of maintaining this uptime is having an Incident Management process in place to restore your services in the event of an interruption or unplanned downtime. Incident Management processes are typically used by SRE, DevOps, NOC and other IT teams to respond to incidents that affect services and work on restoring their uptime.

Monitoring began by using software agents to capture data from infrastructure, operating systems, and applications. These agents would collect metrics and events from these systems to understand the health of the underlying system and the applications. This is what infrastructure monitoring is today.

Running software uses computer memory for data structures and executable operations. How this memory is accessed and managed depends on the operating system and the programming language. Many modern programming languages manage memory for you, and Ruby is no different. Ruby manages memory usage using a garbage collector (also called gc). In this post, we’ll examine what you, a Ruby developer, need to know about Ruby’s gc. Use the links below to skip ahead in the tutorial.

In the middle of January 2020, I got a notification about the upcoming Mattermost hackathon that was being hosted on the HackerEarth platform. I checked out the hackathon page but I forgot about it the next day when I went to work. One morning, I was surfing the internet sipping my coffee and landed on a website that discussed why employee churn rate is high in organizations.

As our enterprise customers build out large, multi-cluster Kubernetes environments, they are encountering an entirely new set of security challenges, requiring solutions that operate at scale and can be deployed both on-premises and across multiple clouds.