Containerized private minion (CPM) release notesRSS

Improvements

• Improved container self-identification logic

Improvements

• Upgraded dependency version to enhance security

Improvements

• Upgraded dependency version to enhance security

New features

Minions now capture more page metrics when you run a simple or scripted browser check with synthetic monitoring!

• firstPaint and firstContentfulPaint paint performance values are now being collected.
• longRunningTaskCount is now being computed ( longRunningTasksAvgTime, longRunningTasksCount, longRunningTasksMaxTime, longRunningTasksMinTime).
• Navigation timing metrics are now being collected: loadEventStart, loadEventEnd, unloadEventStart, unloadEventEnd, domComplete, domInteractive, domContentLoadedEventStart, domContentLoadedEventEnd.
• All of these values are available as attributes on the SyntheticRequest event, in Insights, NR1, and on the monitor results page.

Refer to Google's Performance and navigation timing API's for more details:

• Google's User-centric Performance Metrics contains detailed information about its Paint Timing API and longRunningTasksCount.
• Google's Navigation and Resource Timing Load Performance Assessment contains detailed information about its Navigation Timing API.

Improvements

• Removes support for Oracle JDK and adds support for openJDK.
• Removes dangling Docker network connections at boot.

Features

• Adds support for new format Private Location Keys with unique synthetic monitoring prefixes. Current Private Location Keys will continue to be supported.
• Supports running Private Location jobs from EU based accounts.

Fixes

• Fixed an issue related to running the CPM managed by a private Kubernetes cluster

Features

• Users can now define variables exposed to the scripted monitors via a local JSON file

Fixes

• Watchdog Alerts can now be disabled from the Private Locations page on the Synthetics user interface

Improvements

• Further improvements to minion application logging to sanitize key parameters when debug logging is enabled. See security bulletin NR19-04.