13. Release Notes
- 13.1. Supported Platforms
- 13.2. Compatibility
- 13.3. Supported Docker Compose Environments
- 13.4. Supported Docker Environments for Collector Service
- 13.5. What’s New in 7.7.0
- 13.5.1. Improved discovery and reduced overhead with Collector Service
- 13.5.2. Support for Multicast Discovery
- 13.5.3. Reduced default metrics set in Monitoring Library 2.0, minimizing bandwidth utilization
- 13.5.4. Improved flexibility in security configuration for Collector Service
- 13.5.5. Improved isolation for observability traffic
- 13.5.6. New standalone Collector Service executable simplifies Observability Framework deployments
- 13.5.7. Monitoring Library 2.0 now enabled by default under specific conditions, making it easier to use remote debugging
- 13.5.8. Disallow unrealistic values of polling_period, to avoid errors collecting data for Observability Framework
- 13.5.9. Improved security configuration provides more robust protection for Collector Service
- 13.5.10. Collector Service 7.7.0 works with Monitoring Library 2.0 in release 7.3.x to improve interoperability
- 13.5.11. Flexible control over Monitoring Library 2.0 enablement using new environment variable
- 13.5.12. Monitoring Library 2.0 security enforced when using an RTI security plugin, elevating security standards
- 13.5.13. Third-Party Software Changes
- 13.6. What’s Fixed in 7.7.0
- 13.6.1. [Critical] Collector Service could crash if application periodic data received before application event *
- 13.6.2. [Major] Collector Service did not delete application event queues from WebSocket event handler when application removed *
- 13.6.3. [Minor] Collector Service could not use builtin QoS profiles when configured to skip default files
- 13.6.4. [Minor] RTI Collector Service sent samples that should have been discarded to the endpoints *
- 13.6.5. Vulnerabilities
- 13.7. Previous Releases
- 13.8. Known Issues