I open my laptop and look over my cases while I slurp down my first cup of coffee. Most of my backlog is waiting on customer updates, or bug fixes. Two of my cases have been marked for closure. Not a bad start for a Monday! A pod CrashLoopBackoff issue was resolved by bumping up memory requests, and the missing metrics issue was solved after applying some Prometheus annotations to the customer’s nginx pods. I notate and close both cases. No sooner do I hear the beep of the badge scanner.
Protecting sensitive data from malicious code and dangerous third parties is a critical task rather than something that should be taken for granted. With that in mind, it's an important - yet often overlooked - aspect of security that users stay informed about what's happening in this niche. After all, data security threats evolve at a staggering pace, and 2023's future cyber-attacks are bound to be as inventive as they've ever been.
This tutorial describes how to install the Telegraf plugin as a data-collection interface with InfluxDB 1.7 and Docker. In Part 1 of this tutorial series, we covered the steps to install InfluxDB 1.7 on Docker for Linux instances. We describe in Part 2 how to install the Telegraf plugin as a data-collection interface with InfluxDB 1.7 and Docker.
InfluxDB Cloud runs natively on AWS. This is great for users that already rely on AWS because it keeps everything (or at least most things, hopefully!) in one place. This can also reduce data latency, if the region you use is geographically close to your data sources. Plus, it’s super easy to get started using InfluxDB on AWS. One of the great things about AWS is that it has a ton of different services and features that allow you to do more with your data.
Cloud monitoring is the process of tracking, reviewing, and managing the health and security of cloud-based systems and applications. Cloud monitoring is essential for any organization that relies on cloud-based applications and services. It provides visibility into the performance of these systems and can help identify potential issues before they cause downtime or data loss.
Peering is great for quality and cost savings, but how do you ensure your network is up to the task? Capacity planning is a classic task that should be very familiar to network operators. Providing the right capacity at the right time is crucial to finding a balance between cost and quality in your network.
“Testing your production environment” refers to the practice of running tests on production servers, using actual data from real users. Production testing doesn’t replace other methods like unit or integration testing. Instead, it extends them. Smoke testing is one approach that Lumigo has implemented to test our own production environments.
The traditional wall between IT operations and IT services—along with tedious, antiquated processes for resolving IT issues—is harmful to a company’s productivity. It’s also soul-sucking for team members. Those conditions hinder data sharing and collaboration. As a result, IT staffers must spend hours on cumbersome tasks rather than focusing on meaningful, strategic projects that make them look forward to their workdays.