What’s new

#Introducing Private Locations Permissions

Private locations allow you to perform monitor checks (internally) within your server and firewall instead of the default Uptrends public checkpoints.

By default, all operators have access to all private checkpoint locations. Operators can create, update, disable, and delete a checkpoint anytime. It is essential to manage the level of visibility and permissions among operators.

With the new Manage Private Locations feature, you can set permission rights for specific operators and operator groups:

• Create — allows operators and operator groups to access and create private locations.
• Edit — allows operators and operator groups to access, edit, and delete private locations.
• Use — allows operators and operator groups to select the private location as a checkpoint to run monitors

If an operator has any of the permissions above, the private location will be visible in the Checkpoints tab of a monitor and accessible in the Private locations menu.

#Support for the Multi-part form is now available on MSA monitors

When setting up a Multi-step API monitor, you can specify a payload (data being sent) as part of a request definition. Before, Uptrends only supported sending one type of content at the same time, even though the HTTP protocol does allow multiple parts to be sent. For example, sending some raw text as well as a binary file as part of a single API call.

With the new Multi-part form option, you can now include multiple types of content in the request body of your MSA steps. This option automatically sets the Content-Type request header to multipart/form-data and lets you specify multiple contents in different types. These types can be plain texts entries or files retrieved from the Vault.

#New MSA feature: Error handling

We’ve added a new Error handling section in the MSA Visual step editor UI. This feature gives you more flexibility in handling MSA step errors, allowing better control and adaptability to dynamic web server behaviors.

Selecting the Continue execution after an error checkbox enables you to ignore errors that occurred in an MSA monitor step. This means that if a certain step encounters any errors (such as a bad request, request timeout, or failed assertion), the monitor will continue checking the remaining steps. Such errors will only be visible in the Step results and displayed as An error occurred during this step. These will not be reflected in any of your Errors overview dashboards or reports.  

This error-handling behavior is similar to that of the Transaction monitors. For more information, refer to the Using ignore errors for optional steps and actions knowledge base article.

#New MSA feature: Data protection

Uptrends collects all your MSA monitoring results from the Checkpoint server, which are then directly stored and retrieved on the Uptrends platform.

With the Data protection feature, you can exclude specific monitoring information from being collected and stored on the Uptrends platform. This feature provides an added layer of security, ensuring that any sensitive information remains within your network environment and is not transmitted externally.

By default, the following checkbox options are enabled, allowing Uptrends to store and display information as part of your MSA monitoring results:

• Collect HTTP headers — collects the HTTP Request and Response headers of your website.
• Collect response content — collects the HTTP Response content of your website.
• Collect resolved IP address — collects the Resolved IP address connection details of your website.

Unchecking any of the checkboxes will prevent the associated information from being sent to the Uptrends platform. Instead, an informational text will be displayed.

Please note that the Data protection feature is already available in Private locations. We are now extending this implementation to our public checkpoint network, such as MSA monitoring.