The Telegraf 1.20.3 release changed the official Telegraf DockerHub image to no longer run the Telegraf service as root. With this change, the Telegraf service runs with the least amount of privileges in the container to enhance security given the wide extensibility and array of plugins available in Telegraf.
Our November update introduces new team settings and, along with them, entirely new options for escalating Signls. This will allow you to make your incident response even more reliable. One application is to create a ‘managers on duty’ teams with full duty scheduling capabilities and escalate missed Signls to such 2nd level response team. As always, you can find all the details in this article.
Recently, I explored the case for Graylog as an outstanding means of aggregating the specialized training data needed to build a successful, customized artificial intelligence (AI) project. Well, that’s true, of course. My larger point, though, was that Graylog is a powerful and flexible solution applicable to a very broad range of use cases (of which AI development is just one).
It is crucial for network admins to fully understand their network topology. Even basic troubleshooting can be needlessly complicated without a network topology diagram which is vital for building and maintaining a network. A network topology diagram shows how the various components work together; it shows the devices, connections and pathways of a network visually so you can figure out how devices interact and communicate with one another.
As I said before, Speed is King. Business requirements for applications and architecture change all the time, driven by changes in customer needs, competition, and innovation and this only seems to be accelerating. Application developers must not be the blocker to business. We need business changes at the speed of life, not at the speed of software development.
Time is of the essence when identifying and resolving issues in your software. The longer it takes for a fix to be deployed, the greater the consequences for your customers. Visibility and speed are core to what makes Raygun powerful and is why today we're excited to continue this journey with our latest feature - Alerting.
KubeCon/CloudNativeCon North America 2021 was a whirlwind of sessions, talks, panels, bonding, and learning. As it was a hybrid event, Civo was represented both in person at a booth that featured Sophia and David from our North American team, as well as virtually through our online booth and talks. Plus, we made an announcement of the General Availability of Civo Kubernetes at the event!
As I approach my first anniversary at Mattermost as a Senior Technical Writer, it’s fun to look back on what has been an empowering year of daily technical learning. When I joined Mattermost, I was new to many of the processes and tools used by the team: A year in, I’ve now introduced, led, and supported enhancements across all of these areas, and more! I’d like to introduce you to our product documentation tech stack and share some key learnings we’ve adopted.
Two popular deployment architectures exist in software: the out-of-favor monolithic architecture and the newly popular microservices architecture. Monolithic architectures were quite popular in the past, with almost all companies adopting them. As time went on, the drawbacks of these systems drove companies to rework entire systems to use microservices instead.
Modern customers demand that their applications are as seamless and error-free as possible. However, building such apps is a herculean task in itself. You need to constantly look out for incoming exceptions and warnings in your app in production. Effective error monitoring is key to resolving such issues before they are discovered by your users and cause a disruption in the quality of your services.
