All recorded observations, metrics are variable measured sequentially in time, called time series, stored as raw data. Raw data is produced by a recorder, which fetches data from a system, device or sensor, data which has not been modified or changed in any way. The data is saved as CSV flat files on disk.
You dont need to record all sort of metrics and parameters. To help you, we have carefully selected and analyzed, for each industry, the most needed metrics for different business cases. And we have grouped and classified these metrics, to build a very efficient data analysis process.
Kronometrix can work with various data from Industrial IoT, ICT, to weather and environment, using several recorders and protocols (Serial, MODBUS, BACNet, SNMP or TCP/UDP). Each data recorder is specialized and designed to work with many sources of data, collecting different parameters and metrics.
Temporary stored by the data recording module for a period (configurable) up to 90 days. Each data recorder will save all collected metrics and parameters under one or many text files on disk. These files are simple, regular CSV text files, universal compatible with any software or system.
Recorders are simple, light software probes, which can extract data from different sources, being able to run interactively or continuous mode. They are developed using Perl5, a dynamic programming language being conservative in CPU and memory usage on different computer architectures.
Built as an open-source software, Kronometrix Data Recording is simple to install, customize and adapt to any business. You can build your own commercial products on top of Kronometrix Data Recording. Check out, our commercial supported Kronometrix IoT gateway for more information.
One recording package
Different business cases
Collects the most important performance and availability metrics from computer systems, and operating systems like Linux, UNIX and Windows operating systems.
Analyzes web application availability and performance, using time to first byte method. Designed for different web stack applications like LAMP, J2EE or Rails.
Keeps track of different enterprise services performance and availability: MariaDB, MongoDB, NGINX, Memcached, Redis or different UDP services NTP, DHCP.
Indoor Air Quality
Connects to a number of indoor air quality sensors to gather several important environment metrics: temperature, humidity, CO2, PM2.5, PM10, TVOC or RADON.
Records data from air quality transmitters, e.g Vaisala AQT420. Included: nitrogen dioxide, carbon monoxide, sulfur dioxide, ozone, TVOC or PM 2.5/10
Supports a variety of weather stations, and different communication protocols, to get different weather data wind, temperature, air pressure, solar radiation and more.
Works with network and traffic surveillance cameras, from AXIS Communications to retrieve various parameters including traffic vehicle statistics.
Access a very large number of industrial electronic devices connected to the MODBUS interface, using ASCII, RTU or TCP modes.
From network equipment to HVAC or UPS utilities, records different metrics and parameters used to troubleshoot or analyze the equipments usage or uptime.
How does it work?
A recorder can use one or many data protocols or access several API interfaces to connect to different sources of data. Example, sysrec, the operating system data recorder, can use SYSCTL or PROCFS interface to read FreeBSD or Linux OS data.
All collected metrics are combined as data messages. A recorder can process one or many data messages at the same time. There can be different data messages: computer system utilization, indoor air quality, or water cubic meters messages.
After establishing a valid connection with the data source, the recorder will start to read and gather all metrics defined under recorder configuration file. The metrics can be read sequential, one by one or asynchronously reading an entire group.
A data message will be saved as a CSV text file, on disk, for later processing and archiving. The CSV format is universal available across different systems. If a data recorder is a multi-data message recorder, then several output files, will be generated.
The recorder is designed as a CLI (Command-Line Interface) application. Such way, the recorder can run and execute as any other regular CLI utility, and help for immediate troubleshooting or debug situations and use-cases.
Separate from data recorders, another utility is responsible to fetch and transport data over HTTP or HTTPS for analysis and visualization. The utility is a memory resident application, designed to run in automatic mode, for long periods of time.
The recorder can switch and run for longer logging activities, fetching and saving data without any data interactions. This is the mode necessarily if you need to record and transport data for consolidation, analysis and visualization.
Get answers from the makers of Kronometrix. No extra tiers, no delays, no bureaucracies. We are building and supporting our own products and services offering you the best support model for your business.