Moving time-series data between two NetEye systems is a common, but often underestimated, challenge. Whether driven by infrastructure migrations, platform refactoring, customer onboarding/offboarding, or environment consolidation, the need to relocate InfluxDB metrics reliably and selectively comes up again and again. We created this repository to address that need from a high-level, operational perspective: enabling self-service…
Read MoreA particular client who operates as an ISP for its customers and corporate departments requested the ability to summarize and display, in convenient graphs, a few metrics related to the bandwidth delivered on switch ports, where the available gateways provide connectivity. The first activity I undertook was to obtain the MIB files and OIDs from…
Read MoreBy default all metrics in InfluxDB are stored forever, but for certain metrics we need to store them for a much shorter time span. One example is when we’re receiving very large amounts of raw data, when we’re much more interested in derived characteristics of that raw data. In this blog we’ll discuss how to…
Read MoreInfluxDB is the database used in NetEye for saving performance data. It guarantees graphic visibility of the data (thanks to the Grafana frontend) and it is very important that the data stored is useful. I’ll give you an example of how simple it can be to produce obsolete data in Influx: Suppose I create a…
Read MoreDuring the course of a NetEye installation, a wide range of performance data is collected. From latency metrics of ping checks, to the saturation data of disks and memory units, to the collection of utilization metrics of various kinds. For all of this data we’ve adopted the open source time series database InfluxDB. The time-aligned…
Read MoreIf you’ve ever had cardinality problems with InfluxDB, you might have discovered that a tag is the likely culprit. Well done! But now your next step is getting rid of that tag, and that’s when you’ll realize that in a time series database, tags play an important role in indexing. Because dropping tags is rather complicated,…
Read MoreChangeLog: – fixed bug: Wrong logrotate settings cause HUGE logfile (NIFDB-2)
Read MoreChangeLog: – fixed bug: Wrong logrotate settings cause HUGE logfile (NIFDB-2)
Read MoreChangeLog: – fixed bug: Wrong logrotate settings cause HUGE logfile (NIFDB-2)
Read MoreRoughly one year ago I started working on a set of backup scripts for NetEye with the following requirements: Cluster support without standby Configuration backups InfluxDB backup MariaDB backup In this post I’ll focus on the journey through my MariaDB backup implementation. Backing up MariaDB is usually a simple task: you run the mysqldump command…
Read MoreAs did for the last year edition, our DevOps team participated at InfluxDays, a conference organized by InfluxData and focused on time series data. We were really looking at the event with excitement, for all the new features InfluxData is putting into the new InfluxDB 2.0. So, apart from grabbing a very nice t-shirt, we…
Read MoreScenario NetEye 4 is a comprehensive monitoring platform which natively supports Icinga 2 checks on remote hosts and devices. Several Icinga 2 checks support an historical view of the status. An example is the firewall interface performance status below, which displays a Performance Graph: Getting a better overview All the graph data generated by the…
Read MoreRunning Ollama locally or on dedicated hardware is straightforward until you need to know whether a model is actually loaded in RAM, how fast it generates tokens under load, or when memory consumption reaches a threshold that affects other workloads. A simple TCP port check confirms the process is alive, nothing more. This tutorial shows…
Read MoreHello to you all. It’s been a while. Don’t worry though, this won’t be a long and technical post. It’s just to let you know I’m doing (almost) well and to tell you about our latest news. The Metrics Challenge In the last year we’ve had a lot on our plate, but this hasn’t affected…
Read MoreOur older customers surely know that, in its earliest releases, NetEye 4 had no support for multitenancy. From a data perspective, there’s just one big bin we throw everything into to be used later. Then, a debate about multitenancy began. Here at Würth Phoenix we’ve discussed at length about the best way to segregate data…
Read More