Service Telemetry Framework Release Notes
Release details for Service Telemetry Framework 1.2
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. Introduction to Service Telemetry Framework release
This release of Service Telemetry Framework (STF) provides new features and resolved issues specific to STF.
STF uses components from other Red Hat products. For specific information pertaining to the support of these components, see https://access.redhat.com/site/support/policy/updates/openstack/platform/ and https://access.redhat.com/support/policy/updates/openshift/.
STF 1.2 is compatible with OpenShift Container Platform (OCP) versions 4.5 and 4.6 as the deployment platform.
1.1. Product support
The Red Hat Customer Portal offers resources to help guide you through installing and configuring Service Telemetry Framework. The following types of documentation are available through the Customer Portal:
- Product documentation
- Knowledge base articles and solutions
- Technical briefs
Support case management
You can access the Customer Portal at https://access.redhat.com/.
Chapter 2. Top new features
The following features are new to Service Telemetry Framework:
- OpenShift Container Platform 4.6
- You can now install Service Telemetry Framework (STF) on OpenShift Container Platform (OCP) 4.6.
- Use OpenShift Container Storage as a storage backend
- STF can now use OpenShift Container Storage (OCS) as a storage backend when requesting Persistent Volume Claims (PVC).
- Monitor Red Hat OpenStack Platform services
- When you use STF 1.2 with Red Hat OpenStack Platform (RHOSP) 16.1.3 or later, you can now monitor OpenStack services, such as Horizon, Ceph, Nova, and Ceilometer.
- Change retention period for metrics storage
- You can edit the retention period for metrics storage in the metrics storage backend, Prometheus.
Chapter 3. Service Telemetry Framework release information
Notes for updates released during the supported lifecycle of this Service Telemetry Framework release appear in the advisory text associated with each update.
3.1. Service Telemetry Framework 1.2
These release notes highlight technology preview items, recommended practices, known issues, and deprecated functionality to be taken into consideration when you install this release of Service Telemetry Framework.
This release includes the following advisories:
- Release of components for the Service Telemetry Framework 1.2 - RPM
- Release of components for Service Telemetry Framework 1.2 - Container
- Release of components for Service Telemetry Framework 1.2 - Operator Container
- Release of components for Service Telemetry Framework 1.2 - Operators
3.1.1. Bug fixes
These bugs were fixed in this release of Service Telemetry Framework:
Previously, invalid storage templates resulted in the inability to set custom
storageClassparameters for OpenShift Container Platform (OCP).
With this release, the ability to set custom storage parameters means that you can use Service Telemetry Framework (STF) with non-default storageClasses in OCP, such as OpenShift Container Storage (OCS).
This release of Service Telemetry Framework features the following enhancements:
Previously, a Service Telemetry Framework (STF) deployment enabled the AMQ Interconnect web interface by default, with no ability to turn it off. This increased the attack surface of an STF instance unnecessarily.
With this release, the AMQ Interconnect web interface is disabled by default. It can be enabled by an administrator by using a new configuration option.
When you use Service Telemetry Framework (STF) 1.2 with Red Hat OpenStack Platform (RHOSP) 16.1.3 or later, you can now monitor RHOSP services, such as Dashboard (horizon), Ceph Storage, Compute (nova), and ceilometer.
An example implementation of this is shown in the STF dashboards provided at https://github.com/infrawatch/dashboards/blob/master/deploy/rhos-cloud-dashboard.yaml in the Service Resource Usage panel.
Service Telemetry Framework 1.2 provides a new parameter to allow specification of the retention period for metrics storage in the metrics storage backend, Prometheus.
The default value remains at
24h. You can edit the value in the ServiceTelemetry manifest by using the