Obcerv 1.x Release Notes
Overview
Obcerv release notes contain the list of new features and known issues in the Obcerv platform and apps.
For the latest highlights, see What's New in Obcerv.
Before you install Obcerv, make sure to review the Obcerv 1.x Compatibility Matrix. For details on installation, administration, and usage, you may refer to Obcerv Documentation.
To learn more about Obcerv, visit the Obcerv product page.
Released: 16 September 2022
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| ESCA-279 | Classifications are now included in the entity_info view. |
| ESCA-285 | Metrics with no associated name or value are filtered from GetLatestMetricValues and logged as a warning. |
| ESCA-287 | Queue size parameters for signals, entities, and attributes can now be configured separately. |
| ESCA-290 | Modifying the Docker registry value is now allowed, enabling you to use a single values file. |
Released: 31 August 2022
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| HASO-400 | Drilling down entity groups is improved with the creation of a filter whenever a grouping element is clicked on. |
| HASO-472 | The severity status for attributes is now displayed when drilling down an entity, similar to how it is done for metrics. |
| HASO-491 |
To quickly show the overall status of your IT estate, View as Summary is now used as the default view in the Overview app. |
| HASO-511 | You can now select up to three Group by dimensions to use as filters. |
Released: 30 August 2022
Released: 23 August 2022
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| ESCA-253 | Timelines and signals in the QuerySignalInfo endpoint are now exposed. By adding the timeline to QuerySignalInfosResponse, requests to the backend are lessened. |
| ESCA-256 | Bucketed timelines for individual signals are now exposed. This allows the retrieval of bucketed signal timelines for a single entity. |
| ESCA-259 | Configuration changes related to WAL data tuning as well as calculating settings based on Kubernetes resources have been implemented for improved performance. |
| ESCA-260 | When entities get evicted from the Obcerv Platform, the App Query Service also evicts the said entities to ensure consistency. |
| ESCA-261 | JOOQ SQL queries and timing are now logged, which can help in diagnosing performance issues. |
| ESCA-264 | GetLatestMetricValues has been added to the API, which can be used to request metrics for direct descendants of an entity. |
| ESCA-266 |
To enable metrics collection by the Kubernetes plugin, the following environment variables have been added to PostgreSQL deployment:
|
| ESCA-270 | To improve resource handling, the main daemon has been split into two separate processes: subscribe to entities and upsert in the DB container (write) and query the DB container for requests from the front-end (read). |
Released: 18 August 2022
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| HAL-42 | In Logs, a search functionality has been added to saved filters. |
| HAD-123 | Tool tips and/or labels for displaying the maximum value are now shown in the Gauge, KPI, and Beeswarm dashboard charts. |
| HAD-124 |
In Dashboards, elements in the Query section are now displayed following material UI grid layout. |
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| HAD-27 | An error in updating template variables when a dashboard widget is saved from the Explore page has been fixed. |
| OC-1328 |
A critical BlackDuck vulnerability, which is a transitive dependency of lerna 4.0.0, has been resolved for URL parser IonicaBizau/parse-url version 6.0.0. |
Released: 2 August 2022
Released: 1 August 2022
Highlights
These are the highlights of this release:
-
The Obcerv Platform now supports entity eviction to automatically purge entities from the system that have not been updated for a long period of time. Since the total number of entities is likely to grow over time, you can configure eviction rules to your particular use case.
New features and enhancements
These are the new features and enhancements of this release:
| Issue key | Release description |
|---|---|
| HP-791 | Support for automatic eviction of stale entities (those which have not received data for an extended period of time). Eviction rules can be configured using the Obcerv operator. |
| HP-1401 | When the count function is used, unit values are omitted from GetMetrics* responses. |
| HP-1423 |
Support for tablespaces within Postgres/Timescale. This is helpful for very large installations when there are constraints on the maximum volume sizes set by a cloud service provider. |
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| HP-1471 |
Manually resizing WAL disks now also updates Postgres tuning settings. |
| HP-1475 | Missing Kubernetes labels have been added to workload pods. |
| HP-1507 | The PL/Java libjvm path setting is correctly replicated in Timescale secondaries. |
Released: 14 July 2022
Issues fixed
These are the issues we have fixed in this release:
| Issue key | Release description |
|---|---|
| HP-1455 | When an existing entity classification gets deleted, some entities can be left enriched with attributes defined in the classification. The issue is caused by how RocksDB handles its cache updates when used in conjunction with Kafka streams. |
| HP-1468 | An error in deploying Obcerv when the cluster can't resolve the node hostname has been fixed. |
Highlights
These are the highlights of this release:
-
Next-level observability platform
Obcerv answers the complex data monitoring needs of today's modern IT operations. As an observability platform for data storage and analytics, Obcerv efficiently manages the volume, variety, and velocity of data from different sources. It is your one-stop shop for storing, accessing, and analysing critical monitoring data. -
Flexibility for lower storage costs
Obcerv collects data from multiple feeds and streams while giving you the ability to define rules and organise entities for targeted monitoring. Through meta-tagging, dimensionality is provided to stored data. Data compression lowers storage costs while ensuring that data fidelity is maintained. -
Contextualized and rationalised alerts
Obcerv correlates data and consolidates alerts from various monitoring tools. Obcerv brings context and meaning to alerts coming from multiple platforms. See Alerting. -
Centralized dashboarding
Data from multiple monitoring sources are visualised in easy to create and shareable native and Grafana dashboards. Obcerv’s forecasting algorithms can also predict business levels right on dashboards. See Obcerv Dashboards and Grafana app. -
Streamlined log investigation
Obcerv can store large amounts of log data for deeper root cause analysis. It is easier to find related log errors while having the convenience to view logs side-by-side or in-line. See Logs. -
Interoperability through scalable APIs
Scalable APIs make Obcerv fully interoperable with a range of applications, ensuring that Obcerv seamlessly works with ITRS and non-ITRS products alike. See API Gateway. -
Modular apps
There are several apps designed for the Obcerv platform. See Apps.Depending on your licensing plan, some apps that may be available to you are the following:
- Grafana
- Capacity Planner
- Overview
- Alerting
You can access these apps through the Web Console, which offers a common user interface for Obcerv apps. See Web Console.
Known issues
These are the known issues affecting this release:
| Issue key | Known issue description |
|---|---|
| CPPUB-114 | Connection attempts fail when the Capacity Planner app uses the Apache HTTP Proxy. This is due to LinkerD preventing the Capacity Planner app from publishing data to Capacity Planner. |
| HP-1387 |
Before successfully completing the setup, an error using the The |
| HP-1433 | When you manually set a Timescale multi-server cluster to only one server using kubectl, Timescale read operations will fail. |
| HP-1434 | If no secondary Timescale is available in a multi-server cluster, Timescale read operations will fail. |