Operations | Monitoring | ITSM | DevOps | Cloud

Incident response in a Network Operations Center (NOC) is cumbersome and time-consuming. There are many steps, many sources where incidents come from, and a long, long list of complexities involved. For instance, for incident response with a NOC, there’s the initial monitoring – Tier 1 functions of “eyes on glass” work of looking at alerts coming in and what they’re for, such as a security breach, performance issue, a hardware failure, among others.

In part 1 of this tutorial, we showed you how to build a large language model (LLM) application that uses retrieval-augmented generation (RAG) to query your own documentation and then test it using a CircleCI continuous integration (CI) pipeline.

As another year at KubeCon + CloudNativeCon (CNC) draws to a close, the latest installment in Chicago might be one of our favorite ones so far! With talks having an ever greater focus on the impact of sustainability and inclusion within the community, we loved getting involved in the conversation about how we can make the cloud a better solution for all.

Maintaining a consistent environment from development to production is one of those challenges that's always easier said than done. It used to be that a small hiccup—like a version mismatch or a misconfigured setting—could have you scrambling to figure out why everything worked perfectly on your local machine but started falling apart elsewhere.