Orchestrated Netprobe 1.x Release Notes
Orchestrated Netprobe 1.x Release Notes Copied
Orchestrated Netprobe has now been integrated into the Geneos Netprobe. There will be no future standalone releases for Orchestrated Netprobe. For updates, see the latest Geneos Release Notes.
Orchestrated Netprobe 1.2.0 Copied
Released: 20 December, 2019
This release delivers the updated binaries for in the ITRS Downloads page.
- Collection Agent 1.2.0
- StatsD plug-in 1.2.0
- Kubernetes plug-in 1.1.2
- Netprobe 5.0.0
- StatsD Java client 1.4.0
- StatsD Python client 1.4.0
Highlights Copied
The main features of this release are listed below:
- Updated Orchestrated Netprobe best practices to use Self-announcing Netprobes.
- Single Kubernetes monitoring Orchestrated Netprobe per cluster.
- Upgraded packages to use Netprobe 5.0.0.
- Added verification for valid timestamps used when measuring message latency.
- Configuring a reporter on each pipeline is now optional if only one reporter has been defined
For more details, see Orchestrated Netprobe documentation.
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| C2-110 | Upgraded Orchestrated Netprobe to use Netprobe version 5.0.0. |
| C2-109 | Updated Orchestrated Netprobe Gateway template to use Self-announcing Netprobes. |
| C2-100 | Configuring a reporter on each pipeline is now optional if only one reporter has been defined. |
| C2-84 | Introduced single Kubernetes monitoring Orchestrated Netprobe per cluster. |
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| C2-113 | Loss of connection to the Kubernetes API no longer causes pipeline processing to abort. |
| C2-112 | Upgraded the following libraries: commons-beanutils, commons-compress, jackson-databind. |
| C2-105 | Added verification for valid timestamps used when measuring message latency. |
| C2-102 | An error is now displayed for duplicate properties in YAML config. |
| C2-97 | Collection Agent now creates the store-directory when it does not exist. |
Orchestrated Netprobe 1.1.1 Copied
Released: 23 October, 2019
This release delivers the updated binaries for in the ITRS Downloads page.
Issues fixed Copied
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| C2-91 | In rare cases, a DockerJSON log contains empty log messages. These are now ignored by the log collector. |
| C2-90 | Error messages for undefined but required config properties have been improved for clarity. |
| C2-89 | Resolves a Collection Agent issue where startup aborts if an environment variable is used for a configuration property that is a non-string data type.A warning is now logged if the configuration contains any environment variables whose values are empty. |
Orchestrated Netprobe 1.1.0 Copied
Released: 2 October, 2019
This release delivers the updated binaries for in the ITRS Downloads page.
- Collection Agent 1.1.0
- StatsD plug-in 1.2.0
- Kubernetes plug-in 1.1.0
- Netprobe 4.12.1
Highlights Copied
Orchestrated Netprobe is a new Netprobe distribution package that includes the GeneosNetprobe along with a new agent called Collection Agent.
The main features of this release are listed below.
- Orchestrated NetprobeOrchestrated Netprobe now supports the mapping of metrics from any source and with any combination of dimensions into Geneos.
- Micro and nanosecond precision is supported in timer metrics.
- Histogram data from custom timer metrics can now be mapped and displayed in Geneos.
- Kubernetes plug-in collects these new metrics:
- Filesystem metrics for containers, pods, and nodes.
- Number of CPU cores for each cluster node.See Kubernetes plug-in configuration reference for details on each new metric.
New features and enhancements Copied
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| C2-80 | The NetprobeRestReporter in the Collection Agent was updated to dynamically map metrics from any source and with any combination of dimensions into Geneos. The changes are applicable only to the Metrics and Attributes dataviews. |
| C2-77 | Timer metrics collected through StatsD can now use microsecond and nanosection resolution, in addition to the default of milliseconds. This feature requires both the StatsD plug-in and StatsD clients to be upgraded. |
| C2-75 | Performance enhancement was introduced to reduce garbage creation, resulting in a more consistent memory usage profile. |
| C2-74 | Mean, min, max, count, and percentile methods have been added to TimerHistogram data points. |
| C2-73 | When Collection Agent starts and loads each plug-in, it ensures that the plug-in’s version is compatible with the agent’s version. If any plug-in is incompatible, startup aborts and logs an error. |
| C2-71 | Custom timer histogram metrics collected through StatsD are now mapped and displayed in Geneos as multiple rows that represent count, min, max, mean, 90th, 95th, and 99th percentile. |
| C2-70 | A suite of filesystem metrics is now collected for nodes, pods, and containers. The metrics are displayed in the Kubernetes-Node-FS-Metrics, Kubernetes-Pod-FS-Metrics, and Kubernetes-Container-FS-Metrics data views in Geneos. |
| C2-69 | The StatsD plug-in and clients for Java and Python now support the use of TCP for sending and receiving messages. UDP is still the default protocol. |
| C2-68 | The Kubernetes plug-in now collects the kubernetes_node_num_cores metric whose value represents the number of CPU cores on a physical node. The metric is displayed in the Kubernetes-Node-Metrics data view in Geneos. |
The information contained in this document is for general information and guidance on our products, services, and other matters. It is only for information purposes and is not intended as advice which should be relied upon. We try to ensure that the content of this document is accurate and up-to-date, but this cannot be guaranteed. Changes may be made to our products, services, and other matters which are not noted or recorded herein. All liability for loss and damage arising from reliance on this document is excluded (except where death or personal injury arises from our negligence or loss or damage arises from any fraud on our part).