Data Visualization
PCE Health could report a high failure percentage for the flow rate (E-82901)
The PCE Health Application tab could report a high failure percentage (possibly as high as 100%) in the Collector Summary section. The collector log indicated the failures occurred because the database cache wasn't ready and wasn't processing collector requests. The issue occurred after services restarted on the PCE data node. This issue is resolved. In this release, restarting services on the data node no longer causes the PCE Health page to report a high failure percentage for the flow rate.
Archived flow data caused high Backlog Disk Utilization (E-84587)
Important
This issue applies to Illumio Core On-Premises customers only.
Unexpected archiving of flow data caused an increase in the archive folder size. The problem stemmed from a special character in the username which caused routine uploading of reference data to fail, which in turn caused flow data to be archived, resulting in an abnormal increase in the size of the flow data archive file. Affected customers would have seen an indication of this in PCE Health > Application > Traffic Summary > Backlog Disk Utilization. This issue is resolved. The PCE now handles invalid characters in a way that no longer causes this problem.
IPv6 address filtering didn't work in Explorer (E-84481)
In Explorer, trying to filter Consumers by IPv6 address returned no matching results. This issue is resolved.
Workload count incorrect in Executive Summary Report (E-84300)
In some environments with workloads that have been paired and unpaired, the Total Workloads count was incorrect in the generated Executive Summary Report (PCE > Reports). This issue is resolved.
Location view in Illumination couldn't reload and display the map (E-84091)
When either end of a connection contained workloads without the Role label in the discovered groups, the Illumination map sometimes failed to reload and display the map. This issue occurred when you clicked the discovered groups on either end of the connection to view the workloads in the group. This issue is resolved. In this release, discovered groups display even when they contain workloads missing the Role label.
Global Explorer async query sometimes failed when Supercluster member experienced Health issues (E-83287)
The PCE Health monitoring feature provides warnings and errors when Supercluster members experience issues. Under these circumstances, Global Explorer asynchronous queries sometimes failed for all members instead of returning data for the healthy members. This occurred only in situations where the PCE consul service was unavailable in a Supercluster region and didn't occur for other PCE Health warnings or errors in a region. This issue is resolved.
Input validation error using Policy Generator (E-82828)
When using Policy Generator, if the ruleset included a rule containing a label_group and Vulnerabilities were enabled, the message "Unexpected input validation error" appeared. This issue is resolved. Policy Generator now works as expected under these circumstances.
Illumination Map became stuck in "loading" state (E-82577)
In rare circumstances, when attempting to visualize an environment with more than 50 unlabeled workloads, the Illumination Map got stuck in the "loading map data" state and didn't display. This issue is resolved.
In Draft View, Illumination Map was slow to display in some circumstances (E-82562)
In environments with many IP lists, it sometimes took more than a minute for the Illumination map to display while in Draft View. This issue is resolved. While in Draft View, the Illumination map now renders much faster overall.
Pagination error after switching filtered views in Explorer (E-82534)
In Explorer, a pagination error occurred when switching between two different filtered views. For example, if you filtered by Draft View > Blocked, scrolled through five pages of filtered results, and then filtered by Draft View > Allowed, the Allowed filtered results began on page 5 instead of page 1, which was unexpected. To show filtered results from page 1, users had to refresh the browser. This issue is resolved. Filtered views now always start on page 1.
Roles didn't display in Discovered Group list page (E-82526)
When viewing details of a Discovered Group by drilling into the group from the Illumination Map, the Role column in the group's Workloads tab was empty. This issue is resolved.
Filters selected in Global Explorer and App Group Explorer appeared in both places (E-82479)
When selecting filters in Global Explorer, the same filters were also selected by default in App Group > Explorer tab. Likewise, filters selected in App Group > Explorer tab were also selected by default in Global Explorer. This behavior was unexpected. The expected behavior is that filter selections apply only in the area of the product from which they are selected. This issue is resolved and filters now apply only where they are selected.
Explorer Results page displayed a message that query results exceed limit (E-82743)
When querying in Explorer, the result pages sometimes indicated that the number of returned results exceeded the configured maximum number in the PCE. The issue occurred because the PCE incorrectly validated the count based on total matches in the traffic database instead of the actual results the user could view consistent with RBAC permissions or the actual number of results after filtering query exclusions. This issue is resolved.
The API parameter
max_explorer_query_timespan_days
was not honored (E-82233)After setting an org's
max_explorer_query_timespan_days
parameter to fewer than 30 days, the option to filter by Last Month still appeared in the API and in the Explore UI, which was unexpected. The Last Month filter option shouldn't be available when the parameter is set to fewer than 30 days. This issue is resolved. Themax_explorer_query_timespan_days
parameter is now honored.X-axis labels were incorrect in the Executive Summary Report (E-82226)
When viewing any of the bar charts, the labels on the x-axis did not appear in chronological order or increment one day per bar. This issue is resolved.
"Visibility Only" Workload Filter didn't work properly (E-74231)
Applying the "Visibility Only" workload filter didn't reduce the Connected App Groups count reliably and could be changed again after a refresh. This issue is resolved.