Operations | Monitoring | ITSM | DevOps | Cloud

A summary of the Log4j vulnerability, and key takeaways for SREs.

Data visualization is the process of translating large data sets and metrics into charts, graphs, and other visuals. The resulting visual representation of data makes it easier to identify and share real-time trends, outliers, and new insights about the information represented in the data. Using CircleCI webhooks, we can gather data on workflow and job events. In this tutorial, I will lead you through the steps to create a React-based dashboard to visualize this data.

Software applications consist of interconnected systems - each providing a specialized service towards the common goal of meeting a business need. As with any network, an efficient data exchange mechanism is key to its functionality, effectiveness, and responsiveness. In the past, data exchange was performed using polling requests. At regular intervals, a system would make a request to get the latest information or find out if there is an update to deal with.

CircleCI’s scheduled pipelines let you run pipelines at regular intervals; hourly, daily, or weekly. If you have used scheduled workflows, you will find that replacing them with scheduled pipelines gives you much more power, control, and flexibility. In this tutorial, I will guide you through how scheduled pipelines work, describe some of their cool use cases, and show you how to get started setting up scheduled pipelines for your team.

The database/sql package in the Go standard library maintains a pool of connections so that all queries going through a single *sql.DB instance will reuse the same pool. This is great because you get a connection pool out of the box. But what if you need to share the same connection pool across processes? How do you use the same API in different processes but still reuse the same pool?

Rancher Desktop has been in development for just over a year with the open question: when do we have a 1.0.0 stable release? Along the way the scope has expanded, it was ported to run in more places and the development team has grown. All of this happened as we worked out if Rancher Desktop would be useful for people, what features people want to use and what are good ways to build it. We are finally ready to answer that 1.0.0 question.