1.0.00 enhancements and patches
For a list of recent updates and enhancements across multiple versions, see Release-notes-and-notices.
BMC applies upgrades as described in BMC Helix Upgrade policy . BMC applies upgrades and patches during Maintenance windows .
1.0.05
Security enhancements
BMC PATROL for Cloud Foundry 1.0.05 patch contains the following third-party software upgrade for security enhancement:
- json-20240303.jar
- commons-collections4-4.4.jar
- commons-lang3-3.17.0.jar
1.0.04
Security enhancements
BMC PATROL for Cloud Foundry 1.0.04 patch contains the following third-party software upgrade for security enhancement:
- jackson-datatype-jdk8-2.14.1.jar
- jackson-databind-2.14.1.jar
- jackson-annotations-2.14.1.jar
1.0.03
Security enhancements
BMC PATROL for Cloud Foundry 1.0.03 patch contains the following third-party software upgrade for security enhancement:
- jackson-databind-2.13.3.jar
- reactor-netty-1.0.20.jar
1.0.02
SpringShell/Spring4Shell vulnerability alerts
BMC Software is alerting users to the SpringShell/Spring4Shell vulnerability that requires immediate attention in BMC PATROL for Cloud Foundry 1.0.
A zero-day exploit for the vulnerability CVE-2022-22965 (code named Spring Shell or Spring4Shell) was publicly released on March 30, 2022.
Date: April 8, 2022
Issue
A detailed description of the vulnerability (CVSS v3 rating: 9.8) can be found here: Spring4Shell Vulnerability 
.
Follow the BMC Security Advisory Note 
on BMC Community for continuous updates and details about this issue.
If you have any questions about the problem, contact BMC Support.
We recommend that you immediately apply the fix as described in this topic.
Resolution
This patch upgrades the following jars and removes the vulnerable jars:
Earlier version | Upgraded version |
|---|---|
spring-web-5.3.17 | spring-web-5.3.18 |
spring-core-5.3.17 | spring-core-5.3.18 |
For BMC Helix Operations Management:
- Create a deployable package by using the 1.0.02 version.
- Deploy the patch on the PATROL Agent.
No changes are required to the existing monitor policies. If you want to create new monitor policies, use the 1.0.02 version.
For more information, see Creating deployable packages 
.
For TrueSight Operations Management:
Download and install the patch.
1.0.01
Support for Microsoft Windows and OpenJDK
PATROL for Cloud Foundry supports the following OS version and OpenJDK version:
- Microsoft Windows Server 2022, x86-64
- OpenJDK 11.x
For more information, see System requirements.
1.0.00
Automatic discovery of Applications and Components
After you configure the Cloud Foundry domain, the KM automatically discovers the configured application topology and components. With this KM, manage the configured infrastructure effectively and efficiently.
Monitoring of Application, Event, and Component health
Cloud Foundry Applications
In application monitoring, the KM can:
- Monitor the availability of the applications
- Monitor the CPU, Memory, and Disk utilization of the applications
- Configure filters to include or exclude applications based on organization, space, and application name
For information about how to configure the applications, see Configuring-the-Cloud-Foundry-KM.
For a list of metrics, see Cloud Foundry Application Instance monitor type.
Cloud Foundry Events
In event monitoring, the KM can:
- Configure filters based on event type, actee name, organization name, and space name
- Configure the type of event (alarm, warning, information) for each filter
- Monitor the number of events that meet the event filtering criteria
For information about how to configure the events, see Configuring-the-Cloud-Foundry-KM.
For a list of metrics, see Cloud Foundry Events Filter monitor type.
Cloud Foundry Components
In component monitoring, the KM can monitor the following Infrastructure components:
Component | Description |
|---|---|
Diego Cell | Monitors the cell health, CPU, memory, and disk utilization. For a list of metrics, see the Diego Cell monitor type. |
Diego Brain | Monitors the locks held by the system components, CPU, memory, and disk utilization. For a complete list of metrics, see the Diego Brain monitor type. |
Diego Database | Monitors the active locks, request latency, and LRP attributes. For a complete list of metrics, see the Diego Database monitor type. |
Router | Monitors the total routes, latency, and file descriptors. For a complete list of metrics, see the Router monitor type. |
UAA | Monitors the global and in-flight requests. For a complete list of metrics, see the UAA monitor type. |
Syslog Scheduler | Monitors the CPU, memory, and disk utilization. For a complete list of metrics, see the Syslog Scheduler monitor type. |
Cloud Controller | Monitors the VM health and outstanding requests. For a complete list of metrics, see the Cloud Controller monitor type. |
Cloud Controller Worker | Monitors the CPU, memory, and disk utilization. For a complete list of metrics, see the Cloud Controller Worker monitor type. |
TCP Router | Monitors the average connect time, average queue time, and number of routines. For a complete list of metrics, see the TCP Router monitor type. |
Syslog Adapter | Monitors the CPU, memory, and disk utilization. For a complete list of metrics, see the Syslog Adapter monitor type. |
Loggregator Traffic Controller | Monitors the CPU, memory, and disk utilization. For a complete list of metrics, see the Loggregator Traffic Controller monitor type. |
Consul Server | Monitors the CPU, memory, and disk utilization. For a complete list of metrics, see the Consul Server monitor type. |
Doppler | Monitors the CPU, memory, and disk utilization. For a complete list of metrics, see the Doppler monitor type. |
Cloud Controller Worker | Monitors the CPU, memory, and disk utilization. For a complete list of metrics, see the Cloud Controller Worker monitor type. |
NATS | Monitors the CPU, memory, and disk utilization. For a complete list of metrics, see the NATS monitor type. |
For information about how to configure the components, see Configuring-the-Cloud-Foundry-KM.
Option to enable or disable monitoring
Monitor the application, event, and one or more Infrastructure components depending on your requirements. The KM provides a simple interface with an option to enable or disable monitoring of these entities while configuring the KM.
Detailed annotation messages
The KM provides detailed annotation messages with possible corrective actions in case of any failure. These annotations help you resolve the issue and configure the policy successfully.
Monitor type | Attribute |
|---|---|
Configuration Status | |
Connection Status | |
Monitoring Status | |
Monitoring Status | |
Monitoring Status |
Simple configuration
The web-based configuration interface lets you manage the monitoring and filtering configuration easily. Using a single configuration screen, you can configure the Cloud Foundry domain, applications, events, components, and their filters.