Operations | Monitoring | ITSM | DevOps | Cloud

At JFrog, we believe in practicing what we preach by “drinking our own champagne.” This means that we not only develop and deliver market-leading products but also utilize our own solutions in our development processes. When it comes to managing development environments, we aim to implement the best-in-class approaches.

Infrastructure as Code (IaC) has emerged as a cornerstone for efficiently managing and provisioning infrastructure. Among the many tools available, Terraform has gained unparalleled popularity, offering a declarative approach to defining and deploying infrastructure. But as organizations increasingly embrace IaC to achieve scalability, consistency, and agility, a critical challenge emerges: how to ensure compliance and authorization for infrastructure changes.

As the landscape of real-time monitoring evolves, so does the diversity and complexity of use cases that our community brings to Netdata. Our mission has always been to democratize monitoring by making it accessible, powerful, and scalable for everyone. With the rapid growth of our user base and their expanding needs, it's become clear that our plan structure must evolve to maintain this mission sustainably.

It's completely normal to feel a little overwhelmed and stressed out at work these days. Technology has collaboration moving at the speed of light, and time away from screens is at an all-time low, blurring the lines between work and personal time. Plus, it's hard to ignore the multitude of tech outages that have been making headlines lately, leaving teams anxiously on edge. When you are a professional with on-call cycles, the potential of outages adds another level of complexity to the mix.

Memory is a surprisingly difficult thing to get right in cloud environments. The amount of memory (also called RAM, or random-access memory) in a system indirectly determines how many processes can run on a system, and how large those processes can get. You might be able to run a dozen database instances on a single host, but that same host may struggle to run a single large language model.

HAProxy Kubernetes Ingress Controller 1.11 is now available. For our enterprise customers, HAProxy Enterprise Kubernetes Ingress Controller 1.11 is coming soon and will incorporate the same features. In this release, we enhanced security through the adoption of rootless containers, graduated our custom resource definitions to v1, made them easier to manage, and introduced support for the QUIC protocol.

Is your DevOps tool stack out of control? I feel like every day, I talk to someone who feels this pain. The technological golden age of the past few years created a lot of niche tools, but now that CFOs and boards alike are demanding budget restraint, many of these tools are being scrutinized. The reality of the situation is that it’s not good enough for a tool to do one thing anymore.

journalctl is a command-line utility in Linux systems that allows users to query and view logs collected by systemd's logging service, known as the journal. This logging service captures a wide range of system events, including kernel messages, service status changes, user logins, and more, providing a complete view of system activity. Users can use journalctl to filter logs based on various standards such as time range, severity level, specific units (system services), or even custom fields.