This patch release addresses identified security, compliance, and platform directives for Synthetic Monitoring. It includes fixes for vulnerable libraries, data model and read-only field requirements, API access controls, MID Server security and ECC Queue authorization, API Insight data handling, and Synthetic Monitor status display. These updates improve the application's security, compliance, and platform alignment without introducing new monitoring capabilities.
- Create and manage synthetic tests to replicate end-user transactions for critical services.
- Get real-time notifications for performance degradations or outages before they impact users.
- See related services for synthetic tests to determine incident impact.
- Visualize synthetic test results, track KPIs, and share insights with stakeholders.
Changed
- Synthetic Monitoring is updated to address platform and compliance requirements that include alignment with data model and read-only field requirements, API access controls for Stats API and GraphQL Aggregate API calls, and removal of unsupported data model exceptions.
- MID Server security and ECC Queue authorization have been strengthened. Synthetic Monitoring now supports credential access mode validation and ECC Queue authorization requirements for synthetic monitor execution.
Fixed
- Security and platform compliance issues have been fixed for remediation of vulnerable libraries and updates required by platform security directives.
- API Insight data handling has been corrected. Unsupported
$characters have been removed fromcmdb_ci_api_component_recordsdata resources. - Synthetic Monitor status display has been corrected. Status fields now display the appropriate choice labels instead of numeric values.
Not applicable for this application version.
Agent client collector framework
Event Management
Event Management and service mapping core
For discovered APIs feature:
- API Insights and CMDB CI Class Models
Other Requirements:
If you are upgrading from a previous release and want to run monitors from a MID Server, you must restart the MID Server after upgrading.