What’s new

Users can now better protect their Uptrends accounts by applying two-factor authentication (2FA) to their operator accounts. Uptrends supports time-based one-time password (TOTP) two-factor authentication, meaning users can easily configure their login options by scanning a QR code with any authenticator app of their choice.

Account administrators can enforce the use of 2FA account wide, or for each operator in the account individually. After setup, operators will be prompted to enter a six-digit code generated by their authenticator app in addition to their user credentials when logging into Uptrends.

Would you like to show the performance metrics Core Web Vitals and W3C navigation timings of individual steps on a dashboard? Now you can activate the storage of data for this purpose inside the transaction step. Open your transaction and expand the step you want to report on, then enable the “Performance metrics” option in the step settings at the top. Note that this option is only available when you activate the Waterfall setting.

Once enabled, the performance metrics Core Web Vitals and W3C navigation timings are available and allow you to report them on a dashboard using the custom tile Simple data chart. The legend of the tile will indicate which graph belongs to which step, e.g. First contentful paint (step 1) will be shown in there. You can also hover over the graph to get more details.

Operators can now specify which Uptrends newsletters they would like to receive. We have added a new section Newsletter subscription in the Main tab in the Operator settings.

You can choose if you want to receive Feature updates or Checkpoint updates, or both, by selecting Subscribe. If you opted in or out of these Uptrends newsletters earlier, this new functionality will not affect your current subscription settings.

Our Multi-step API monitor type allows users to interact with their critical APIs directly. For some monitoring use-cases, data must be sent to the API, for example when executing POST requests to create a new object, or a PUT/PATCH request to update an existing object. In such cases, it is important to include a Content-Type header to inform the receiving API of the type of data that is coming in (JSON, XML, form data, etc.) so that it knows how to parse the request. An API will commonly return errors if it receives a request body without a Content-Type header.

Up until now, such headers had to be added to the Multi-step API monitor step(s) manually. As of this update, we are automatically detecting the content type, and adding the correct Content-Type header, for JSON, XML, or form data request bodies. This change will help users configure POST, PUT, and PATCH requests in their Multi-step API monitors.

If you are confronted with errors that you regard to be incorrect, we offer the option to clear errors and recalculate the SLA (service level agreement) data for you.

Until now you had to create a (standard) Support ticket to request the error clearance and include the required information in writing. We’ve made that easier by adding a button Clear multiple errors to the bottom of the monitor Check details dialog.

Clicking the button will open a ticket specific to error clearance. In the ticket, you have to include the mandatory data to ensure that Support receives the info necessary to process your request. The mandatory information includes the monitor (groups) that are affected and the date range. Optionally you may fill in the checkpoints and status code.