OES 3.3.X Release Notes

This Version is deprecated

The below versions are deprecated.

Version 3.3 (25th November 2020)

New Features

Cluster tagging - This feature allows you to create and assign tags to the clusters to suit their business logic. It can be used as a platform for teams to capture knowledge. Tags can be derived from metadata of the logs, like filename, service name or analytical data like classification, or user assigned data like feedback string. From 3.3, you can provide multiple tags to select which tags are displayed as part of a cluster and which tags can be used as part of filters. You can pre-define actions associated with the cluster tags notifications.
Select Scoring Logic - Now you have the option to select the scoring logic from the following options:
- Canary: This scoring is used for canary analysis, it does the comparison between v1 and v2 log files and finds the risk shift. Here all v1 log clusters are used as normalization factors.
- Autonomous Scoring: This scoring is used for build analysis , it considers only the errors, warnings occurring in v2 log file, doesn't consider common(V1,V2) events and calculates the risk. Here all v2 log clusters are used as normalization factors.
- Definite Scoring: This scoring is simple and more interpretable, it just looks at the number of v2 unique errors, warnings and scores them by a fixed amount. It doesn't have any normalization factor and it doesn't scale scores based on log file size.
- Comprehensive Scoring: This is similar to build scoring but it considers common clusters between v1 and v2 along with v2 unique clusters. Here all v2 log clusters are used as normalization factors.
Visibility - Approval Gates are control points in software delivery. You can add approval gates as stages in Jenkins, Spinnaker. In OES, approval gates are triggered by events from tools like Jenkins, Spinnaker. It then collects all the information and provides to the user to approve. Once approved, Gate triggers the next stage of the pipeline. OES 3.3 comes with the Visibility feature which allows you to provide information for decision approval gates. In order to approve or promote production, now you can collect information from previous stages along with the information from tools like Git, Jenkins, etc. and also comments/notes from the approver. This data will allow you to make an informed decision.
Life Cycle Management (LCM) 1.1 - The LCM 1.1 comes along with the following features:
- Enable Secure Service Communication. mTLS - By default the spinnaker services communicate with each other over http protocol and there is no secure layer for communication. This feature is intended to provide a secure layer for internal communication between spinnaker components. Self signed certs generated using k8s native cert manager. Installing these certs on each of the spinnaker services. Enabling https on all the services.
- Enable Secure API for Spinnaker (Security for webhook) - Secure API for Spinnaker would be to enable X.509 authentication for the webhooks.
- Enable Metrics to Monitor (Prometheus default) - Prometheus based monitoring to be implemented and alert manager based notifications to be configured to ensure timely alerts incase of issues.
- Pipeline Update Promotion Process.

Fixed Issues

List of data sources are not appearing in the GUI.
In deployment verification page tag dropdown is not showing custom tags.
Switching between tabs cluster data is not showing in UI.
Visibility feature config : If the user deleted all the connectors from the table, still the table header should be retained for the user to add back the connectors.
Visibility : Connectors are saving without selecting account name.
Sometimes Analysis reports in deployment verification page is not appearing.
Auto population of metric templates are shown as empty.
Approval gate status icon is not changing after approving or rejecting a gate in the approval screen.
Display the connector tabs in the approval screen visibility data section in the alphabetical order.
Navigation menu icons not aligned.
Perceived Risk graph is appearing empty.
The feature selection component should be displayed only after the service is created.
Get log template API is failing.
After reclassification - Service list is shown as empty - impact of this cluster score box is shown as empty.
Moving across the connector tabs is not refreshing the content.
The service selector window doesn't refresh/update and displays incorrect values.
In Deployment verification page - after reclassification trigger same canary seeing extra count in clusters.
Default values for Threshold(%), High & Low missing.
Deployment verification - Stop analysis is not working as expected.
Log Analysis > Time Analysis graph is not stable.
Click on application not able to see service list in right side section.
Unable to do reclassification for previous runs.
Pagination "Next" & "Previous" buttons are enabled even if we have a single page of entries in Datasource.
Log Analysis section is flickering in a canary analysis report when the mouse cursor is hovered on the navigation menu items.

Known Issues

Previous comments for reclassification of one canary are still appearing after re-run and update.
DOWNLOAD Debug data on the Deployment verification page is not working.
OpsMx logo is not hyperlinked.
Metric Analysis - Sorting is not available.
Firefox browser - The Deployment Verification page has a shift left effect.
"Download Cluster Info" is not working under Log Analysis.
UI should show loading message while waiting for back end data.
UI System level error handling and error message needs to improve.
Edit metrics Select and unselect is not working in API's selection.
If we manually Edited log template custom topic and reclassify the same cluster then changes are not effecting into Log Template page.
Without adding an Application details - user should not able to go to add Services or other sections.
The plot in time based correlation tab is displaying incorrect data from actual log data.
While adding two metrics to the metric template (one is having data and the other is having no data) failure for service is happening.
OES Version string auto update based on build tag.
Log analysis should be success when no logs to analyze.
Expected to see an error message when the user is logged out and then redirects to the login page.
Download debug data option is missing.
Deployment verification - log template : Can't edit to add new tags.

Version 3.3.1 (8th December 2020)

Fixed Issues

Firefox browser - The Deployment Verification page has a shift left effect.
If we manually Edited log template custom topic and reclassify the same cluster then changes are not effecting into Log Template page.
Log analysis should be success when no logs to analyze.
Deployment verification - log template : Can't edit to add new tags.

Version 3.3.2 (15th December 2020)

Fixed Issues

Java - Logs + metrics with newrelic was not working.
Deleting applications from visibility service was not working.
Autopilot connector API was failing.
Endpoint to Delete the SAPOR application from spinnaker was not working.
Issues with OES Open LDAP Authorization and File Based Authentication and Authorization.
After editing and saving the log template the tags created were not appearing.
In Edit Log template, tags against each cluster tag pattern was always shown as the first tag.
Issue while adding log pattern in template.
Multiple tags with same name were getting created.
Canaries API to fetch the analysis results not working.
"500 Oops something went wrong" error message shown at the time of login.

Version 3.3.3 (16th December 2020)

Fixed Issues

Show more on the analysis page was effecting multiple clusters.
Tags on similar cluster are not getting transferred from one run to another.

Version 3.3.3.1 (29th January 2021)

Fixed Issues

Include special characters in the Log Template to match with the log lines to be tagged properly.

PreviousOES 3.4.X Release Notes NextOES 3.2.X Release Notes

Last updated 2 years ago

Was this helpful?

Version 3.3 (25th November 2020)

New Features

Cluster tagging - This feature allows you to create and assign tags to the clusters to suit their business logic. It can be used as a platform for teams to capture knowledge. Tags can be derived from metadata of the logs, like filename, service name or analytical data like classification, or user assigned data like feedback string. From 3.3, you can provide multiple tags to select which tags are displayed as part of a cluster and which tags can be used as part of filters. You can pre-define actions associated with the cluster tags notifications.

Select Scoring Logic - Now you have the option to select the scoring logic from the following options:

Canary: This scoring is used for canary analysis, it does the comparison between v1 and v2 log files and finds the risk shift. Here all v1 log clusters are used as normalization factors.
Autonomous Scoring: This scoring is used for build analysis , it considers only the errors, warnings occurring in v2 log file, doesn't consider common(V1,V2) events and calculates the risk. Here all v2 log clusters are used as normalization factors.
Definite Scoring: This scoring is simple and more interpretable, it just looks at the number of v2 unique errors, warnings and scores them by a fixed amount. It doesn't have any normalization factor and it doesn't scale scores based on log file size.
Comprehensive Scoring: This is similar to build scoring but it considers common clusters between v1 and v2 along with v2 unique clusters. Here all v2 log clusters are used as normalization factors.

Visibility - Approval Gates are control points in software delivery. You can add approval gates as stages in Jenkins, Spinnaker. In OES, approval gates are triggered by events from tools like Jenkins, Spinnaker. It then collects all the information and provides to the user to approve. Once approved, Gate triggers the next stage of the pipeline. OES 3.3 comes with the Visibility feature which allows you to provide information for decision approval gates. In order to approve or promote production, now you can collect information from previous stages along with the information from tools like Git, Jenkins, etc. and also comments/notes from the approver. This data will allow you to make an informed decision.

Life Cycle Management (LCM) 1.1 - The LCM 1.1 comes along with the following features:

Enable Secure Service Communication. mTLS - By default the spinnaker services communicate with each other over http protocol and there is no secure layer for communication. This feature is intended to provide a secure layer for internal communication between spinnaker components. Self signed certs generated using k8s native cert manager. Installing these certs on each of the spinnaker services. Enabling https on all the services.
Enable Secure API for Spinnaker (Security for webhook) - Secure API for Spinnaker would be to enable X.509 authentication for the webhooks.
Enable Metrics to Monitor (Prometheus default) - Prometheus based monitoring to be implemented and alert manager based notifications to be configured to ensure timely alerts incase of issues.
Pipeline Update Promotion Process.

Fixed Issues

List of data sources are not appearing in the GUI.

In deployment verification page tag dropdown is not showing custom tags.

Switching between tabs cluster data is not showing in UI.

Visibility feature config : If the user deleted all the connectors from the table, still the table header should be retained for the user to add back the connectors.

Visibility : Connectors are saving without selecting account name.

Sometimes Analysis reports in deployment verification page is not appearing.

Auto population of metric templates are shown as empty.

Approval gate status icon is not changing after approving or rejecting a gate in the approval screen.

Display the connector tabs in the approval screen visibility data section in the alphabetical order.

Navigation menu icons not aligned.

Perceived Risk graph is appearing empty.

The feature selection component should be displayed only after the service is created.

Get log template API is failing.

After reclassification - Service list is shown as empty - impact of this cluster score box is shown as empty.

Moving across the connector tabs is not refreshing the content.

The service selector window doesn't refresh/update and displays incorrect values.

In Deployment verification page - after reclassification trigger same canary seeing extra count in clusters.

Default values for Threshold(%), High & Low missing.

Deployment verification - Stop analysis is not working as expected.

Log Analysis > Time Analysis graph is not stable.

Click on application not able to see service list in right side section.

Unable to do reclassification for previous runs.

Pagination "Next" & "Previous" buttons are enabled even if we have a single page of entries in Datasource.

Log Analysis section is flickering in a canary analysis report when the mouse cursor is hovered on the navigation menu items.

Known Issues

Previous comments for reclassification of one canary are still appearing after re-run and update.

DOWNLOAD Debug data on the Deployment verification page is not working.

OpsMx logo is not hyperlinked.

Metric Analysis - Sorting is not available.

Firefox browser - The Deployment Verification page has a shift left effect.

"Download Cluster Info" is not working under Log Analysis.

UI should show loading message while waiting for back end data.

UI System level error handling and error message needs to improve.

Edit metrics Select and unselect is not working in API's selection.

If we manually Edited log template custom topic and reclassify the same cluster then changes are not effecting into Log Template page.

Without adding an Application details - user should not able to go to add Services or other sections.

The plot in time based correlation tab is displaying incorrect data from actual log data.

While adding two metrics to the metric template (one is having data and the other is having no data) failure for service is happening.

OES Version string auto update based on build tag.

Log analysis should be success when no logs to analyze.

Expected to see an error message when the user is logged out and then redirects to the login page.

Download debug data option is missing.

Deployment verification - log template : Can't edit to add new tags.

Version 3.3.1 (8th December 2020)

Fixed Issues

Firefox browser - The Deployment Verification page has a shift left effect.

If we manually Edited log template custom topic and reclassify the same cluster then changes are not effecting into Log Template page.

Log analysis should be success when no logs to analyze.

Deployment verification - log template : Can't edit to add new tags.

Version 3.3.2 (15th December 2020)

Fixed Issues

Java - Logs + metrics with newrelic was not working.

Deleting applications from visibility service was not working.

Autopilot connector API was failing.

Endpoint to Delete the SAPOR application from spinnaker was not working.

Issues with OES Open LDAP Authorization and File Based Authentication and Authorization.

After editing and saving the log template the tags created were not appearing.

In Edit Log template, tags against each cluster tag pattern was always shown as the first tag.

Issue while adding log pattern in template.

Multiple tags with same name were getting created.

Canaries API to fetch the analysis results not working.

"500 Oops something went wrong" error message shown at the time of login.