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.
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.
Starting with Go 1.13, Go modules are the standard package manager in Golang, automatically enabled on installation along with a default GOPROXY. But with other GOPROXY options like JFrog GoCenter, as well as your own Go module packages you need to keep secure from public view, what kind of configuration should you choose? How can you keep your public and private Golang resources from becoming a tangled knot?
During the past few months while working on Icinga DB, we have tested our existing libraries on how we work with data and how we present them programmatically. Maybe it was because we were doing something new with Icinga DB or we weren’t entirely happy with the existing code. In any case, it was time for new libraries :-). The IPL – Icinga PHP Library was born. And we want to share that work starting with ipl/Sql an OOP SQL abstraction for PHP.
Gradually, brick by brick, we will get the necessary toolkit to build a company and maintain it. If on previous occasions we have emphasized the importance of monitoring a company’s IT systems, today we will review what it is and what advantages we when we centralize monitoring. The goal is pretty simple: we want to have maximum control over the IT of a company moving unbridled to the summit.
