Releases: CESNET/telemetry
Releases · CESNET/telemetry
v1.1.0
What's Changed
- makefile - fix typo in HEADER_FILTER in #26
- github-action - doxygen now reports warning as errors in #28
- telemetry - holder - mark move constructor as default in #30
- appFs - non-blocking fuse loop in #29
- Telemetry - add symlink in #25
- GitHub-actions: build examples in #31
Full Changelog: v1.0.0...v1.1.0
v1.0.0
New release! (Telemetry & AppFs v1.0.0)
I am excited to announce the 1.0.0 release of the Telemetry library and AppFs library! This release marks the first stable version, offering robust telemetry data collection and FUSE-based filesystem integration for seamless real-time data access.
Key Features:
- Telemetry Library:
- Provides efficient data structures for telemetry metrics (files, directories, etc.).
- Supports real-time monitoring and collection of telemetry metrics like CPU usage, memory usage, uptime, and more.
- Flexible data retrieval, storage, and manipulation for monitoring solutions.
- AppFs Library:
- Integration with Telemetry for exposing telemetry data through a FUSE (Filesystem in Userspace) interface.
- Access telemetry data as a mounted filesystem, allowing standard filesystem operations for monitoring and data manipulation.
Changes in 1.0.0:
- Initial Stable Release: This is the first stable release, including all core functionalities for Telemetry and AppFs.
- FUSE Support: Enable the user-friendly mounting of telemetry data directories for real-time access.
- Enhanced Example Implementations:
- Simple Example: Demonstrates a minimal setup for collecting telemetry data (e.g., process ID, version, uptime).
- Advanced Example: Illustrates detailed data collection across multiple virtual servers and structured output of metrics.
How to Use:
- Install the libraries by following the installation guide in the README.
- Use the provided example applications to start collecting and managing telemetry data