What’s new

#HTTPS monitors now support the latest Edge and Chrome user agents

It is now possible to select the latest Edge and Chrome versions in the user agent settings for HTTPS monitors. This allows you to automatically send the latest browser and operating system information during HTTP requests, without having to manually set the value.

Read more

#Track your custom metric performance with minimum, average, and maximum values

The Custom metrics list and chart now display the minimum and maximum values, alongside the average values already available for each metric. These values are color-coded and plotted on the diagram, making it easier to spot trends and compare performance over time.

Read more

#Monitor templates can now be filtered

Monitor templates can now be filtered by name for easier access.

Read more

#HTTPS monitors now support additional TLS and HTTP versions

HTTPS monitors now support TLS 1.3, HTTP/2, and HTTP/3 versions, enhancing security and performance for monitored endpoints.

When you select any of these options, only checkpoints that are capable of supporting these versions will be available for use. Alternatively, you can select Negotiate to enable the client and server to automatically negotiate for the HTTP version to use, preferring HTTP/2 over HTTP/1.1.

While support for HTTP/3 is available, it is not currently recommended for use due to compatibility and stability limitations.

Read more

#Postman API monitors now auto-retrieve and display collection variables

When you import a Postman collection that uses variables like {{VariableName}} in requests, scripts, or environments, the Postman API monitor now automatically detects and displays these variables as pre-defined monitor variables. You can easily populate their values either through plain text or using the Vault. This is helpful when authenticating with APIs that require a username, password, or secret key.

This behavior also works similarly to Multi-step API variables.

Read more