OIDC group synchronization with read-only LDAP federation Fixed an issue that occurred when OIDC group synchronization was enabled alongside a read-only LDAP federation. The OIDC mapper attempted to modify LDAP-managed group memberships, resulting in the error: Not possible to delete LDAP group mappings as mapper mode is READ_ONLY. The synchronization logic now respects the LDAP…
Read MoreImportant: GLPI security update Type/Severity NetEye Product Security has rated this update as having a high security impact. Topic An update for the glpi packages is now available for NetEye 4. Security Fix for NetEye 4.50 Summary This is the list of vulnerabilities patched in this update: For details on how to apply this update, which includes the…
Read More
Turning Relevant Campaigns into Actionable Security Content To prioritize detection rule deployment based on threats that could realistically affect our organization or customer environments, we’ve developed an intelligence-driven detection model. Rather than prioritizing rules solely by mapping MITRE ATT&CK techniques and addressing coverage gaps indiscriminately, the model uses threat intelligence to identify which campaigns, behaviors,…
Read MoreIn my previous post, I was pointing out how an LLM context should be handled with care, and how there’s a better and worse way to basically interface with it. It’s not enough to “prompt in a clear way” or pack tons of customizations inside a CLAUDE.md file. In part 1, which you can read…
Read MoreNATS: Fix multi-tenancy configuration corruption in cluster environments When executing commands such as neteye install –restrict-services-to nats-server, neteye tenant config apply, or neteye satellite config create from a cluster node while nats-server was active on a different node, the shared /neteye/shared/nats-server/conf/multi-tenancy.conf configuration file could get corrupted. Unreplaced template placeholders (such as @@ACCOUNTS@@, @@TORNADO_IMPORTS@@, and @@TELEGRAF_IMPORTS@@)…
Read MoreUpgrading an existing NetEye cluster to 4.49 introduces a networking question that’s easy to underestimate. The existing environment may already have everything we normally associate with a NetEye cluster: a corporate network for frontend access and integrations, a private trusted network for internal cluster communication, and the corresponding virtual IPs. With Kubernetes entering the architecture…
Read MoreImportant: Grafana security update Type/Severity NetEye Product Security has rated this update as having a medium security impact. Topic An update for the grafana packages is now available for NetEye 4. Security Fix for NetEye 4.49 and 4.50 Summary Four medium-severity CVEs were fixed (CVSS 4.3–5.4). Three concern permission scoping: alert rules listable from folders a user may…
Read MoreWelcome to version 4.50 of our NetEye Unified Monitoring Platform. As you log in, you’ll be greeted by the wide-open autumn meadows of Alpe di Siusi, the largest high-altitude plateau in Europe, with the jagged peaks of the Gruppo delle Odle and the distinctive ridge of Seceda rising in the distance. Their pale rock faces…
Read MoreA quick overview of the new native numerical calculation feature available in Jira systems. It’s something we’ve been waiting for a long time. Introduction The ability to perform calculations within an integrated management system is one of our most requested features. This need is most pressing in large organizations, where such data increasingly forms the…
Read MoreAt NetEye we’re always working towards more and more integration with Kubernetes. The NetEye Operator is the first piece of that journey we’re working on, with the goal of obtaining a component that ships as a Kubernetes operator rather than as an RPM. The process of building it gave us a rare opportunity, a chance…
Read MoreAgentic coding tools promise to move beyond code completion. Instead of asking an AI assistant to generate a function or explain an error, we give an agentic coder a goal and let it inspect a repository, plan a change, edit several files, run tests, and iterate. That shift is powerful, but it also changes the…
Read MoreIntroduction Managing a service desk is usually straightforward when a team is small. A request comes in, someone picks it up, and the work gets done. Things become more complicated when the service desk grows, though. Different teams start supporting different services, people work in shifts, some requests require specific skills, and the workload is…
Read MoreScheduling Roulette Imagine you’ve applied a deployment, run kubectl get pods, and now there they are: Every Pod is neatly sitting on some node. It feels a bit like roulette. You spin the wheel, and the Pod lands wherever it happens to land. The good news is that wheel is not as random as it…
Read MoreWhen using Kubernetes on bare metal, exposing a LoadBalancer Service usually requires some mechanism to make the Service IP reachable from the surrounding network. With Cilium, one possible solution is L2 Announcements. Cilium can answer ARP or NDP requests for the LoadBalancer IP, effectively making that IP reachable from the local network. At first sight,…
Read MoreHmmm, that question sounds familiar… maybe I wrote about something similar in the past, for instance Would You Use an AI Chatbot to Write Your Blog Post? That time I was saying that a lot of people were beginning to write their blog posts with the help of AI. And that the result was wonderful…
Read More