Start monitoring today and get 20% off on your first invoice. Available on all Uptrends plans.

Recent changes in Uptrends

We're always improving! Stay up-to-date on the latest product updates.

Below you find all information on the latest features that were implemented in Uptrends. However, you may have suggestions for new features yourself and also be interested in testing our new features before they are officially released. Go to

  • Feature request to read more about how to submit your request.
  • Beta programs to find out about features that are in the beta phase and to register for the program.

October 2020

  • Integration for AlertOps New

    If you follow the "Recent changes in Uptrends" you have probably noticed that during the last months we were busy adding new integrations to our app. The integrations are needed to get your message (notification on an Uptrends alert) across to the communication or incident management system that your company uses.

    The latest addition to the growing flock of integrations is the AlertOps integration. AlertOps is an incident management and response platform. AlertOps integration type

    For a description of how to define an AlertOps integration check out this article at AlertOps.

  • Multi-step API monitors: User-defined functions New

    We have added user defined functions to Multi-step API monitors. The functions are available for each step and can be used to convert a value. There are two types of functions: mapping and regular expression.MSA step with user defined functions

    The mapping function lets you enter value pairs that can be used to substitute values.

    The regular expression function can be used to extract a value by applying a regular expression to an existing variable value. Once a function is defined, it can be used in a response variable definition by selecting the option "Execute function" and referring to the previously defined function.

September 2020

  • Waterfall PDF export New

    This feature has been on the wish list of many users for some time. Now you can export your Waterfall graphic for a Full page check (FPC) monitor. 

    The PDF files can be used as a backup of your waterfall data, for later reference. Or you can use PDFs right away to share the waterfall results by email or as printed copies.

    To create a PDF of a Waterfall: open the check details of a monitor check and click the button Export PDF at the top of the Waterfall graphic. The PDF is created and automatically downloaded to your default download folder.

  • Share free tool results New

    We offer quite a range of free tools on our website (and in the Uptrends app). Now we have added the option to share the results that these tools generate.

    To share test results: just run the tool and wait until the test has finished and the results are shown. Above the results, an additional line is shown inviting you to "Share these results" followed by a link (URL). Copy the link from here and share it with the people that are also interested in the test results.

    Note that sharing works only on our website, not within the Uptrends app.

August 2020

  • Integrations for Opsgenie, Statuspage, and Zapier New

    We already provide quite a number of integrations, and have added three new ones to the list: Opsgenie, Statuspage and Zapier are now predefined Uptrends integrations. To learn more about the setup of the integrations, check out the Knowledge base articles for Opsgenie and Statuspage. More information on the Zapier integration will follow soon.

  • Response header check tool New

    We at Uptrends offer a number of free tools and are always looking to add more gear to the toolbox. Our newest addition is the Response header check tool to check out and verify your server's HTTP response headers. The information you get from the tool is useful when troubleshooting problems.

    Access the Response header check tool online and get more information about it. In the Uptrends app go to Apps & Extras > Response header checker to open the tool.

  • Concurrent monitoring in public beta stage Change

    A few weeks ago we introduced Concurrent monitoring as a private beta feature to a small number of users. This feature now enters the public beta stage and is available to all Business and Enterprise plan subscribers. Note that the feature doesn't fit into the setup of the other subscription plans and therefore will not become available for those plans.

July 2020

  • Check interval in the 'Monitors' overview Improvement

    We've added some extra information to the 'Monitors' overview ('Monitors' drop-down menu > 'Monitors'). Aside from the main information for each monitor (name, type, URL, creation and latest modification dates, and so on) it now also lists the check interval for each monitor. This helps you to quickly spot which monitors run at a normal or slow interval (e.g. 5-60 minutes) and whether some of your HTTPS or API monitors could be bumped up to 1-minute monitoring for faster error detection and more precise uptime data.

    Monitor overview check interval

  • New Microsoft Teams integration New

    Integrations are key in getting your Uptrends alerting notifications sent out, ensuring they reach the right people over the right channels as quickly as possible. To facilitate this process, Uptrends offers several predefined out-of-the-box integrations, so you can easily link your Uptrends alerting to external applications or platforms. In this update, we've added a new predefined integration with Microsoft Teams, the chat and collaboration tool in Office 365. Using this new integration, you'll be able to automatically send Uptrends alert notifications to the appropriate channel(s) in your Microsoft Teams environment.

    We've written up a complete, step-by-step guide on how to set up the Microsoft Teams integration.

June 2020

  • UTF-8 support for Multi-Step API monitoring Improvement

    A Multi-Step API (MSA) monitor allows you to accurately test the functioning and performance of your APIs, by setting up a sequence of API calls that check the full extent of your API's capabilities. Using the primary HTTP methods (GET, POST, PUT, PATCH, DELETE), you can interact with your API, set assertions to verify the correct response, and then reuse variables from previous responses in subsequent steps. Often, that process will involve sending some request body to your API.

    In the latest version of Uptrends, we've added UTF-8 support for such request bodies. Previously, there would be issues correctly encoding certain characters, which could lead to the monitor returning errors. Now that we're supporting UTF-8, we're able to correctly encode characters like diacritical marks and non-Latin languages. Practically, that means you're now able to include essentially any special character or language you like in the request body of your Multi-Step API calls.

  • Extended set of available user agents Improvement

    For certain monitor types, we allow you to set a user agent in the Advanced tab of the monitor settings. The user agent you choose is then passed along with the HTTP request, which informs the receiving server about the "user's" environment. For example, using the appropriate user agent, we can tell the server that we're using Chrome 83 on a Windows platform. This could prompt the server to send specific content, optimized for that environment.

    In addition to allowing custom user agents, the user agent option in the monitor setting came with a predefined list of commonly used user agents. We felt this list was getting a bit outdated, so we're extending it in this release. The newly updated list of predefined user agents now contains the correct user agents for recent versions of most modern browsers.

  • Support for certificate rollover in a single sign-on setup. New

    It's now possible to use more than one public key certificate for single sign-on. At the single sign-on settings section on the account settings page you can now choose to use all vault items inside a vault section. This will allow you to upload new certificates issued by your SSO provider, even before they are actually used by the provider (this is called certificate rollover).

    You can even automate this process by uploading the certificates using our API. We do recommend that you remove any old certificates that are no longer used, as this is considered a security best practice.

  • Ping tool New

    Uptrends offers a number of free tools that come in handy when monitoring your website, services or servers.

    The Uptrends Free tools family just got a new member - the Ping tool. It does what the command line 'ping' does, but the Ping tool presents the results in a user-friendly way. Another big advantage is that you can ping a server from multiple checkpoints in one go. All results will be presented in one dashboard. When hovering over the checkpoint tiles on the dashboard, you will get extra info about the traceroute.

    In the Uptrends app, go to the menu item Apps & Extras > Ping test to try out the new tool.

    Ping tool with results

May 2020

  • Checkpoints: Upgrade to Chrome 83 Improvement

    Our checkpoints have been upgraded to the latest version of Chrome, which is Chrome 83.

    Uptrends keeps the checkpoint browsers up-to-date, because this is crucial for your monitoring. The Chrome browser of your customers or users will update to a new version automatically. A new browser version could introduce a problem with your website or web service and you would want to know about that as quickly as possible. That is why we upgrade our checkpoints to the most recent versions of browsers when they become available. You stay in sync with what your customers or users have and monitor what they experience with the latest version.

    If you want to find out about the features or changes in the latest Chrome version, check out the Chrome Enterprise release notes.

  • Dashboards and tiles: new filter for successful checks (OK results) New

    Sometimes you have a situation where an error has appeared for quite a long time and you wonder: "What was the last time that the check returned an OK result and my server or services were still doing fine?" If there are many errors in a row, it gets tedious to find that one OK result, just before the problem started. By using this new option, you filter out the noise (the unconfirmed and confirmed errors). You shorten the list of errors to OK results only and find more easily that point in time when things still were fine.

    In dashboards and tiles you can filter the data that is shown by checkpoints, error level and time period. Until now, the error level allowed you to filter by everything, unconfirmed and confirmed errors or only confirmed errors. We have added the option to filter on successful checks (OK results) as well now. For dashboards, the setting is at the top right of the dashboard:

    Monitor log OK error filter

    The new filter option also exists in the settings for tiles. Find out more about dashboards and tiles in the Uptrends Academy Course: Lesson "Dashboard 101".

    Note that, the setting will also affect your reporting. The filtered data, as shown in the dashboard, will be used for data exports and scheduled reports.

  • Screenshots and Waterfalls: available for Business subscriptions New

    Screenshots and Waterfalls are features of a Transaction monitor. They are described in the KB articles Working with Transaction Screenshots and Working with Transaction Waterfalls.

    These features were enabled for Enterprise subscriptions only. Now they are available for Business subscribers as well.

    As a Business subscriber, you now can enable the Screenshot and Waterfall options for each transaction step. In addition the Screenshot is available in your list of actions to add to transaction steps. When you add a Screenshot action, you determine yourself where in the sequence you want to take the screenshot. Keep in mind, that each waterfall and transaction counts towards the transaction monitor credit calculation. The details for the calculation are described in Transaction monitor credit calculations.

    In the KB article Using transaction screenshots and waterfalls you find detailed info on how to set up and make the most out of these features.

April 2020

  • SLA target Page load time:  higher precision Improvement

    In the Uptrends app you can set up your Service Level Agreements (SLAs), based on contracts that you have with your providers or customers. The SLA definition allows you to configure minimum or maximum requirements, which are called SLA targets. The values measured against these targets can be viewed in the SLA Overview dashboard.

    One of the SLA targets that can be configured in the SLA definition is the Page load time. Until now you could enter only an integer to set your target for the load time. We have improved that by adding two decimals in the latest version of Uptrends, so you can use higher precision when setting the load time target. For example, in the past you could set the target to 1 or 2 seconds. Now you have the option to set the value to 1.5 seconds or even 1.75 seconds.

  • Monitors: Alert conditions are now Error conditionsChange

    In your Monitors, there was a tab called Alert conditions. We felt that the name was not describing correctly what the tab is about. After all you do not define conditions here for generating alerts, but you define conditions for the detection and generation of errors. Hence the tab got a new name and now is called Error conditions. The functionality and the content of the tab is still the same!

    In case you are working with Monitor templates - these will also have the new tab name to be consistent.

  • Custom integrations: Error type IDNew

    Integrations are used to notify a person or system, when an alert was generated by one of your monitors. An integration can be a simple e-mail or an SMS or one of the predefined system integrations, like for Slack or PagerDuty. Or you can send out a customized message to another third-party system. 

    The information that is available in the Uptrends app is sent to the third-party system using system variables. When you compose the message in your custom integration, you will add those system variables. The details of how to do this are explained in the KB article Setting up a custom integration.

    There were already many system variables available, as described in the KB article above. However, one piece of info was missing that has been added now: the Error type ID.

    The error type ID is a code (4-digit number) that is Uptrends specific. You can find a list of error types (with ID and explanation) in the KB article Error types. A common error type ID is "3002", which relates to an HTTP connect failure.

    When composing the body of your request, insert the variable as  {{@alert.errorTypeId}}.

    For example, one line in the request body could be: {"Error type ID": "{{@alert.errorTypeId}}" }

March 2020

  • File uploads in transactionsNew

    Transaction monitoring offers a rich set of actions you can use to interact with the browser: clicking on buttons, typing text, scrolling the page, checking content - even creating screenshots.

    One important action was still missing: the ability to upload files. Thankfully, that’s now possible!

    It works in the following way: you can upload the appropriate file(s) to the vault first. Use the vault item type “File” to indicate you’re storing a file in the vault. Then, inside your transaction definition, use the Set command pointing to the file upload element on your page. The Set command lets you point to an item in the vault - choose the file item you just stored there, and your file upload should run smoothly!

    Please note that when you create a transaction recording using the Recorder tool, it will capture the file upload action, but not the file itself. You will have to go into the vault yourself to provide us with the appropriate file. After you upload your recording, you’ll see the Set command that corresponds to your recorded file upload. Just change its value to the file from the vault, and you’re good to go.

  • Audit log: entries made by UptrendsChange

    The Audit log function (visible in the Account menu) lets you inspect all of the changes that were made in your account setup, and by whom. Occasionally, if you ask Uptrends Support to help you out, we’ll make some changes for you in your setup. So far, it wasn’t clear whether a change was made by you or another user in the account, or whether it was made on your behalf by Uptrends. The audit log has now been improved to clearly indicate which changes were made by Uptrends.

February 2020

  • Mobile app available for Single Sign-On usersNew

    The Uptrends mobile app, which shows the current status of your monitors and alerts along with uptime and performance charts, couldn't be accessed so far by users who use Single Sign-On to log into Uptrends.

    A new version of the app is now available for iOS and Android. This latest version of the app works together with the Uptrends web app: once you're logged into Uptrends on your computer, find the Mobile apps page in the Apps & Extras menu. You can generate a login code (QR code) there that can be scanned by the mobile app. You'll be logged in automatically once the code is scanned.

  • Public Status Page display optionsNew

    The Public Status Page feature has some new options. First, you can specify whether the uptime status for each hour/day/month should be displayed chronologically, or most recent data first.

    Additionally, you can specify whether to display your monitors alphabetically by name, or sorted by error status.

    Finally, it's now possible to publish a custom comment (consisting of a title and text) that you can use to provide extra information to your users. This custom comment will be displayed at the top of your public status page.

January 2020

  • Automating checkpoint tasksNew

    When you're into automating repetitive tasks related to your Uptrends setup, you may have been wondering about which checkpoint servers are available for your monitors, how to specify which monitors should run in which countries or continents, and how to obtain a full list of servers for the countries you're interested in - possibly to create a whitelist for your firewall configuration.

    The Checkpoint API could already return a full list of checkpoints, including the appropriate IP addresses, but there was no way to figure out which continents contains which countries, and the checkpoints contained in each country.

    You can now use the new /CheckpointRegion functions to retrieve all of this information. Check it out in the Checkpoint API section of our Swagger docs.

  • APIs for dashboards, reports and public status pagesNew

    New API methods have been added to clone and modify custom dashboards. On top of that, scheduled reports (for sending automatic email reports based on a dashboard) can now be added using the API. This combination allows you to take a custom dashboard you've prepared, and use that as a master template to generate dashboards and scheduled reports for specific teams or customers who wish to receive email reports.

    Additionally, there are new API methods for managing Public Status Pages. It's probably not very efficient for you to use the API to manage one or two public status pages, but if you're interested in using the protected status page function (read more here) to publish status information to separate teams or interested parties outside your organization, then it might be useful to automate that using the API.

  • Breaking API change for creating Multi-Step API monitorsChange

    The Monitor API lets you create or update monitor settings. For setting up a Multi-Step API (MSA) monitor using the API, you previously had to use the ApiStepDefinition attribute. This attribute no longer exists, and is split into two separate attributes: the MsaSteps attribute is an array that contains the complete list of MSA steps. PredefinedVariables is the other new attribute, which contains the complete list of predefined variables.

December 2019

  • Responsive design and mobile device testing in transactionsNew

    When you've recorded a transaction script to test user scenarios in a browser, you want the test circumstances to be as close to the end-user's experience as possible. These circumstances include the size of the browser window (test your site in large, maximized browser windows, but also on smaller screens, and everything in between) and different device types (desktop browsers vs mobile/touch devices).

    Uptrends' new transaction technology, which lets you build and test your own transaction scripts, now also includes browser window size settings to test responsive designs for desktop browsers, and device simulation settings to test your site for mobile/touch devices. You can pick predefined or custom window sizes, set user agent values, or choose from a wide range of mobile devices, including iOS and Android devices, for mobile simulation testing. Bandwidth throttling options are also available.

    These options are now available for Full Page Check monitors and Transaction monitors. For more information, please look at the mobile website monitoring page.

  • Geographical display in CDN toolNew

    We've added a new function to our free CDN tool, which helps you to test your CDN and DNS distribution settings and performance. In addition to getting performance data, IP addresses and HTTP response header info (including CDN debug headers) from 40+ locations worldwide, you can now also inspect this data displayed on a world map. Go check it out, do a CDN tool test run!

  • New transaction technology! New

    For many years, Uptrends customers have been using transactions to test browser-based user journeys in their web applications. Each transaction is carefully crafted by Uptrends Support, which means that customers get a carefree experience for getting stable transactions running. But relying on Support does mean that you can't do everything yourself, instantly.

    Today, we're happy to present our new transaction technology, which includes the option for a complete self-service experience. Many customers have already been trying it out for the last six months (thank you!) and we're now extra confident to give it to all Business and Enterprise customers.

    If you have existing transactions - They still work in the same way. We're planning to convert them to the new transaction technology at some point, so please talk to us when you're ready to try it. Head on over to your transaction settings to find more information.

    If you're creating new transactions using the Transaction Recorder - The recorder tool will ask you if you want to test and tweak the recording by yourself first, or if you want to continue collaborating with Support. You'll always keep both options, and the cost stays the same. Just choose what you're comfortable with.

    Not sure what to do? Just try making a recording, choose self-service and see what the experience feels like. Recording uploads are free of charge and unlimited. As always, you can contact us to discuss your options.

    Ready to discover the new transaction approach? Follow the Academy course.

  • Self-Service Transactions: Wait action New

    Transactions consist of a sequence of Actions, which are organized in Steps. A typical action could perform a navigate, click or content check operation in the browser. These actions are designed to wait long enough until the browser is done loading and ready to receive the next operation.

    However, sometimes it's useful to take control of the pace of your transaction script a bit more. It was already possible to use a Wait for element action to explicitly wait for an element to appear on the page. You can now also use a Wait a fixed time action to suspend the transaction for a fixed amount of time. Please note that this option increases your overall transaction running time. Excessive wait time values will cause your transaction to time out if it exceeds the maximum running time.

  • Custom metrics available to Business accounts New

    The Custom metrics feature lets you dig deeper into your API data. This feature was available to Enterprise accounts so far, but we've decided to let Business users take advantage of the rich feature capabilities as well. The only thing you need is to set up one or more Multi-Step API monitors. Read more about setting up custom API metric monitoring.

November 2019

  • Convenient Single Sign-On using a subdomain New

    Single Sign-On (SSO) has been available as an option in the Enterprise plan for quite a while now. It works well for users who use Identity Provider initiated SSO. For users who are limited to Service Provider initiated SSO, it wasn't so convenient to start the login process.

    We've introduced a new option to make this better. You can now request a subdomain (for example that will be linked to your Uptrends account. Once this setup is complete, you can simply access that URL to initiate the login process. Please read more information in the SSO overview page.

  • Transaction Recorder for SSO users Improvement

    Many Uptrends users use the Transaction Recorder to make a recording of user journeys in their web app. Those recordings can then be further customized in the self-service transaction editor.

    The recorder tool (which is an extension in your Chrome browser) requires users to log into their Uptrends account, but that wasn't possible yet for users who sign into Uptrends using Single Sign-On. The recorder is now finally available for all users (Business and Enterprise plans). Welcome SSO users, happy recording!

  • Self-Service Transactions: Alternative selectors New

    The Transaction Recorder captures the web page elements you click and interact with during a recording. For each page element, the recording should contain a sufficiently unique and constant reference to get correct and repeatable results each time the transaction gets executed. These references are called selectors

    Once a recording has been uploaded, you can review the recorded selectors in the self-service transaction editor. A new feature in this process is that you can now switch between different alternatives: during the recording process, we'll capture several possible selectors for each element you record. In each case, you can decide which one is more useful for getting repeatable results.

October 2019

  • Monitor log export optionsNew

    When you go to the Monitor Log dashboard, you can inspect each individual measurement that was performed for your monitors. Within that data, you can filter on specific monitors, and you can filter on error level to focus on error situations.

    But sometimes you need more options to do faster searches, custom filters and sorting. Excel works great for wading through long lists of data, so you can use the Excel export option for that. You can generate Excel files on the spot, or have them sent to you by email. There's a similar export option for PDF.

    So what's new for the export function in this release? Using the tile settings, you can now customize which fields are included in the export. The export has a lot more fields than the ones visible in the dashboard itself, including step times for transactions and Multi-Step API monitors, custom metrics, several timing fields, download sizes, resolved IP address and more.

  • Custom API metrics New

    API monitoring just became even more powerful! Our Multi-step API monitoring allows you to monitor the performance and behavior of your APIs. Aside from tracking response speed and uptime, it also lets you identify key data points returned by your API, and set alerting on those data attributes when they don't meet the criteria you specify. Many Uptrends users use these features to identify unexpected results in their API's responses.

    However, our new Custom Metrics feature unlocks a new level of API monitoring. It can extract specific data points from the JSON or XML data returned by your API, and store it as custom data metrics in your Uptrends account. It will plot any numeric data that your API can return, allowing you to spot trends in your data that you couldn't previously see. This powerful new feature is available for free for all Uptrends Enterprise users. Read more about setting up custom API metric monitoring.

  • Breaking change in PUT requests for Monitor API Change

    We've made a breaking change in the APIv4 Monitor API. This API lets you retrieve monitor info and update, clone or delete monitors. The change only applies to API users who are using the PUT method to update existing monitors.

    So far, the PUT method was the only way to make changing to a monitor definition via the API. The API team recently decided to start introducing the PATCH method as well. PATCH will be the new method for making partial changes to a monitor definition. Partial changes are useful when you only want to change one setting, or a few settings, without having to provide the entire monitor definition. In contrast, a full change specifies the full monitor definition, including all fields - often by retrieving it first using the GET method.

    Until recently, the PUT method would accept both partial and full updates. This is no longer true: when you specify a partial update (i.e. not listing the full monitor definition) using the PUT verb, the request will fail and return a 400 Bad Request. If you are facing this issue, simply change the HTTP verb to PATCH, which will accept your partial update.

    If you were already using the GET/PUT scenario (retrieving a monitor definition using GET, making a change in the JSON and sending the entire thing back using PUT), you don't have to do anything.

    For more information, please look at the API Swagger documentation.

  • Monitor API supports more fields New

    The Monitor API is currently limited in the number of fields it supports. Today's update is the first of a series of updates that will expand the Monitor API. Aside from the IsActive field, which lets you enable or disable a monitor, the GenerateAlerts field was added. The Monitor API was previously limited to specific monitors, but now lets you control these fields for all monitor types.

  • Managing maintenance periods New

    Maintenance periods are time windows you define for a specific monitor in order to suppress monitoring and/or alerting. This is useful if you're planning maintenance for your web platform, which would cause false positives in your alerting. You can create maintenance periods for individual monitors, or use the monitor template feature to define one or more maintenance periods and copy them to groups of monitors.

    However, planned maintenance sometimes gets rescheduled, which means you need to update your maintenance periods in Uptrends. Until recently, there was no convenient way to find out which maintenance periods already existed in your account, aside from inspecting each monitor individually.

    You can now use the new Maintenance periods option in the Monitors menu to review all maintenance periods. By default, maintenance periods are shown for the All monitors group, but you can narrow this filter to specific monitors or groups. You can also open up the tile settings in the overview to zoom in on a specific time period (e.g. all maintenance periods for next month). After selecting the right filters, you can use the Delete button to remove all maintenance periods for the selected monitors and selected time period. Additionally, the Clean up button lets you get rid of all maintenance periods that are in the past.

    Lastly, if you're inspecting a maintenance period of a specific monitor, you can select the corresponding periods for all other monitors by using the new Select similar periods link. This lets you jump straight into the list of periods if you want to remove them.

September 2019

  • Power upgrade for email alertsNew

    When one of your monitors generates an error, you can send alerts to all kinds of third party systems including Slack and PagerDuty, to your phone, or via good old trusty email. If you're using the email channel as a way to process incoming alert messages, you may want to automate that using email rules or some other form of automated processing.

    In order set up effective processing rules, it can be useful to look for certain words or phrases inside the email content. While each alert email coming from Uptrends always starts with the same content (citing the monitor name, time and date of the alert, and so on) you can include a fixed custom text in an alert email by specifying the Message field in the escalation level of an alert definition.

    This custom text is now the key to more powerful and flexible alert email content! Inside your custom text, you can now include references to dynamically generated data that is relevant to the alert or the failing monitor (this data is expressed using system variables) and to custom fields you can specify. Custom fields are text values that you can specify for each specific monitor. For example, you can use custom fields to keep track of the data center where each site is hosted, which rack(s) in that data center, which checklist should be used to resolve issues, or anything else that is specific for each monitor. You can now output that additional data as part of your alerting, simply by making a reference to a custom field inside your custom alert text. Use the {{@CustomField()}} notation to create these references. For more information about system variables and custom fields, please read the documentation for setting up custom integrations, which already included these options.

August 2019

  • Custom operator timezone in monitor logImprovement

    Enterprise account operators can specify their own timezone setting, if they are working in a different area in the world than the account's main timezone. In the monitor log dashboard (or any dashboard that displays the monitor log tile), you can now open the monitor log tile settings and choose between Account timezone and Operator timezone. The date/time values in the log will be displayed in the appropriate timezone. Furthermore, both timezone values will be displayed in a popup when you move your mouse cursor over that date/time value. If you prefer to always view the monitor log in your own operator-specific timezone, you can create your own custom dashboard that uses this new setting.

  • Excel export row limit increasedImprovement

    The Excel export used to be limited to 65,535 rows. We've now increased this limit: technically, an Excel report can contain about a million rows. However, please consider the amount of data this would produce, and the amount of time it takes to generate such a file. Please try to limit your exports to a maximum of several hundreds of thousands of rows.

  • More system variables in custom integrationsNew

    When you build a custom integration to send alerts from Uptrends to another system, you can use system variables to build your message content. We've added four more options to the list of available variables, allowing you to specify information about the alert definition and escalation level that triggered the alert. Read the full list of variables for customized alert messages.

July 2019

  • From Steps to CreditsImprovement

    We have two monitor types that consist of several actions that are executed as a sequence: Transactions and Multi-step API monitors. Longer sequences are more expensive to execute, so long transactions or MSA monitors require more space in your account. Until recently, if you needed more space for transactions, you could purchase additional transaction steps. Similarly, you could buy extra API steps for MSA monitors.

    We haven't actually changed this, but we're giving it a better name. Why was this necessary? The actions in a transaction or MSA are organized in things also called Steps. However, these steps provide a logical separation into distinct chunks. There's no cost involved in keeping things organized, so it was confusing that both the logical separation and the involved cost were using the word step.

    Therefore, the new naming convention is: logical steps are still called Steps. Transactions and MSAs consist of several steps, but the cost of each step depends on what you put in them. The cost for each Transaction or MSA is now expressed in Credits. You'll keep the same amount you had before, we're just giving it a different name.

    In your Monitor overview, Subscription settings and new Invoices, you'll now see the terms Transaction credits and API credits.

  • Staging mode for MonitorsNew

    Back in March, we introduced Development mode for Professional, Business, and Enterprise accounts. Development mode lets you modify and manually test monitors without them counting towards your plan’s allotment of monitors, nor do they affect your SLA or uptime data. Now we’ve added the next step in safely bringing a new monitor live, Staging mode.

    Although Development mode lets you work out most of the kinks in your monitors, Production mode may reveal other issues not evident in the controlled environment of development mode. Moving a monitor (especially Transaction or Multi-step API monitors) can have a negative impact on your data due to unforeseen issues you might want to avoid. To help you out with transitioning from Development mode to Production mode, we've added Staging mode. Staging mode lets you put a monitor into the production environment without the monitor affecting your SLA or Uptime data.

    Monitors in Staging mode do count towards your plan’s monitor allowances, so you must have enough available monitors to bring monitors in Development mode to Staging.

    We have information in our Knowledge Base where you can learn more about Monitor Modes, and Staging’s effect on your data.

May 2019

  • Create copies of your monitorsNew

    You may have a monitor setup where a lot of monitors use a similar setup, but with a different URL, or different checkpoint selections, etc. It's now easier to set this up: you can take an existing monitor definition (perhaps one you set aside in Development mode as a template) and click the Save as... to save a copy! We'll take you straight to that new copy so you can make the necessary changes there. If you want to make a copy, but you don't have enough monitors left in your account, you can still create that copy and put it in Development mode. You can create those for free!

  • Monitor log shows secondsImprovement

    The monitor log dashboard gives you access to each individual measurement that gets executed for your monitors, showing the timestamp of the moment that measurement finished executing. Sometimes, it's useful to know the exact time, in particular when you're investigating an error situation. For this purpose, the timestamps are now displayed more precisely, including the seconds of those timestamps.
    Clicking on a monitor log entry opens the check details for that particular entry, which already displayed the exact timestamps. Did you know that Enterprise account users can choose to display those timestamps in a different timezone? Go to your operator settings to select an alternate timezone, if you're operating in a different timezone than the main account timezone.

  • StatusHub integration in silent modeImprovement

    When you're using the StatusHub integration, you'll know that StatusHub can send you notifications when the status of your services changes. However, you may not need any notifications when your Uptrends monitors alter the status of your StatusHub services. To suppress those notifications, you can now use the new Silent option in your StatusHub integration settings.

  • Operator APINew

    We've added new functions to API v4 for working with operators (i.e. the users / logins in your account). The operator API allows you to create, update and delete operators, along with their off-duty schedules. Read the Operator API docs for more information.

April 2019

  • Groups in Monitor list Excel exportNew

    Monitor groups are a good way to organize your monitors. Groups can be helpful for reporting, but also for creating an organized alerting setup, for easy application of monitor templates, and so on. In the Monitor list in the Uptrends web application, you can see the group membership for each monitor. In this update, we've made sure that this group membership is also included when you create an Excel export of your monitor list.

  • Checkpoint selection in the monitor test functionNew

    When you're editing a monitor, most monitor types let you use the Test button to test your monitor and see whether the results come back as OK. When you click the Test button, you need to select on which checkpoint you want the monitor to be executed. You can choose any of the checkpoints available to your account. In the past, if you wanted to run this test several times, you needed to re-select the checkpoint each time. This has been corrected: we'll preselect the previously selected checkpoint if you run a test multiple times.

March 2019

  • Development mode for monitorsNew

    Sometimes you're setting up a new monitor that requires some testing and tweaking before it's ready to run in production. For example, you may be working on a Multi-step API monitor with multiple HTTPS calls, content checks and variables. Stabilizing that kind of setup just takes a while before it's complete and ready for action.

    Working on these monitors (perhaps you would even like to work on several, separate versions) would be easier if you could have draft versions in your account that don't take up any space (in terms of monitors, API steps or transaction steps) until you're ready to take them into production.

    For this purpose, we're introducing a new concept for Professional, Business and Enterprise accounts: monitors can be switched to Development mode. In the new Monitor mode settings for a monitor, you can switch between Development mode (which means that the monitor won't run, but also won't cost you anything) and Production mode (which is the default: the monitor will run normally in your account, but also counts towards the number of monitors and steps you have in use).

    For more information about the new monitor mode settings, please read our Knowledge Base documentation.

  • Excel export formatChange

    We admit it was a bit overdue: the Excel files produced by the Excel export and Scheduled Report functions are finally producing the common .xlsx format. Until recently, they still used the old .xls format, which required some conversion steps when you wanted to import them in external systems. Happy exporting!

February 2019

  • Monitor Group APINew

    We've added new functions to API v4 for working with monitor groups. The Monitor Group API lets you create, update and delete monitor groups, and it allows you to start/stop all monitors in a group, suppress or resume alerting for all monitors in a group, and add new maintenance periods for all monitors in a group. Read the Monitor Group API docs for more information.

January 2019

  • New alert integration optionsNew

    Uptrends monitors can generate alerts when an error is detected. Those alerts can be sent to a range of so-called integrations: you can use integrations with e-mail, SMS/text messages, phone calls, Slack, PagerDuty and StatusHub.

    Several new options have been added to this list: integrations with VictorOps and ServiceNow are now available, plus a really powerful option to build your own custom integration. This means that Uptrends alerts can now be consumed by any third party system - or your own, if you want to plug alert data into your own API. Go to our main Integrations page for more information, or read more about building custom alert integrations.

  • Alert message logsNew

    Uptrends monitors can generate alerts when an error is detected. Those alerts can be sent to a range of so-called integrations: you can use integrations with e-mail, SMS/text messages, phone calls, Slack, PagerDuty and StatusHub.

    When we detect errors for your monitors, we'll generate alert events according to your alert definition settings - an Error alert when the alert first appears, and an OK alert when the alert is resolved again. You can see those alerts in the Alert status and Alert log dashboards.

    Aside from appearing in those dashboards, alerts are typically meant to generate alert messages - sent to your e-mail, your mobile phone, your on-call team member's pager, or any third party software you and your team members are using to manage incidents and share information with.

    This feature has been part of Uptrends for ages, but it was never really visible where each message was sent, who should have received it, and when.

    Our new Alert message logs are putting an end to this. When you open up the details of an alert in any of the aforementioned dashboards, you'll notice a Messages tab in the popup. That tab will list all of the messages that were generated based on your integration settings. For example, you might see that we sent out an alert via e-mail (and to which recipients), via SMS, to a Slack channel, and via a custom integration that connects to your IT management system.

  • Phasing out Windows Phone app

    Starting February 13, 2019, we will discontinue support for our Windows Phone mobile app. Windows Phone users will no longer be able to run the Uptrends app on that platform.

November 2018

  • Monitor type: IMAPNew

    A new email monitor type is now available: IMAP. Similar to POP3, IMAP is a protocol for reading email from a mail server. The IMAP monitor type lets you connect to your mail server, using credentials from a mailbox account, to verify that the mail service is operating normally.

October 2018

  • Adding a wait step in Multi-step API monitorsNew

    Multi-step API monitors execute sequences of API requests. These requests are executed very rapidly, to give you a clean report of the amount of time it takes to execute them. For some APIs, this may be a little too fast. We've now added special Wait steps that can be placed in between consecutive Request steps. Wait times can be anything up to 60 seconds. For more information, please read the Multi-step API article in our Knowledge Base.

September 2018

  • API methods for maintenance periodsNew

    If you are regularly performing maintenance on your websites and services, you also want to control your monitoring accordingly to avoid getting alerting during your maintenance windows. For each monitor in your account, you can create one-time or recurring maintenance periods to temporarily suspend monitoring, or suppress error alerts during that time.

    We've added new methods to our API v4 that allow you to automate the process of creating, updating and deleting maintenance periods for individual monitors. Additionally, you can add a new maintenance period to all monitors in a group in one go. For more information, please read the documentation in our Knowledge Base.

August 2018

  • Controlling checkpoint fallback behaviorNew

    When you create/edit a monitor, you can select on which checkpoint locations that monitor will run. Many Uptrends users choose to select as many checkpoints as possible (you can select multiple countries or even continents if you want), but sometimes it's useful to have a checkpoint selection that's carefully targeted at a specific region. For each subsequent check, we'll choose one of the checkpoint locations you selected.

    Checkpoint locations may be out of service for short periods of time, due to local network problems or maintenance. We try to minimize checkpoint downtime, but it is possible that several checkpoints are unavailable at the same time. This means that there may be no checkpoints available if you've only selected a few checkpoints. To ensure continuity for your monitoring, the monitor will still be executed, on a fallback location outside your normal checkpoint selection.

    However, this may cause a problem if you are using a whitelisting policy that has whitelisted only specific IP addresses of our checkpoints.

    To resolve this issue, you can do two things:

    • 1. Increase the number of checkpoints you are using for your monitoring. This will greatly reduce the chance that your entire checkpoint selection is unavailable for monitoring.
    • 2. Turn off the fallback behavior: in Account Settings, we've added a new option Checkpoint fallback, which is enabled by default. If you turn the option off, no fallback will occur. Instead, the monitor check will be skipped. A new monitor check will be attempted at the next monitor interval. Please note that this may cause some gaps in your monitoring results.
  • Audit log detailsNew

    Last month, the new Audit Log feature was added: this logging feature is intended to display a log entry for each change that is made in your account, so you can track down all activity in your account. The Audit Log is still being worked on, and we'll continue to add more logging. What's new in this release is that the Audit Log now reveals the details of each change. When you click on a log entry, we'll show you exactly what happened.

    For example, if one of the operators enabled or disabled a monitor, or they changed one of the settings of a monitor, you can see exactly what was changed, by whom, at what time. For each setting that was changed, you can inspect the previous setting and the new setting. This gives you a complete and chronological picture of the history of your account.

  • Monitor type guidanceNew

    When you're setting up your Uptrends account, the most vital step is to create monitors for everything you want to start monitoring. We have about 18 different types of monitors that do very different things, so choosing the right type of monitor can be a little daunting.

    To help you make the right choice, we'll show a help screen that has a brief explanation for each monitor type, along with links to further documentation. Once you've made your choice, we'll take you to the edit screen with the appropriate monitor settings. If you're not sure which type to pick, feel free to switch between monitor types to discover different options!

    The Monitor Types page in the Academy can get you up to speed. Our Knowledge Base contains articles for each individual monitor type.

July 2018

  • Introducing: Audit logNew

    If you have a lot of monitors in your Uptrends account, and if you have a large team working with different monitors, alerting rules and other settings, it may be difficult to keep track of the activity in your account. In particular, you may be interested to see who made the latest changes to a monitor, and when.

    We're adding a new feature called Audit log which will help you with this. The Audit log currently includes all activity connected with creating, changing and removing monitors. Additionally, it tracks activity in the Vault, and it shows the login activity for each operator.

    The Audit log will grow over time as we add more activity tracking. All administrators of Premium, Professional, Business and Enterprise accounts have access to the Audit log via the Account menu.

June 2018

  • Vault section authorizationsNew

    Over the last couple of updates, we've been introducing the Vault as a brand new feature that allows users to store sensitive data (certificates, passwords, etc.) in their account. The only thing missing from the Vault user interface was the ability to assign authorizations to different operators for different sections in the vault. This last missing piece has now been added.

    In the vault section editor, authorizations can now be added and removed for operators and operator groups. Two types of authorizations exist: Full control (allowing operators to add, modify and remove vault items in a section) and View only (allowing operators to use vault items in monitor settings, without being able to see or change the sensitive data stored in that vault item).

  • Checkpoint APINew

    New methods have been added to API v4: you can now use the API to download information about our checkpoint servers (in particular the IP addresses).

    As part of this update, we've added some methods that can be accessed anonymously (without needing an API login account) to download a clean list of IPv4 and IPv6 addresses of our checkpoint locations. You can use these methods to write a script that keeps your firewall updated if you want to whitelist the IP addresses of our checkpoints.

May 2018

  • Multi-step API Monitoring general releaseNew

    The latest release of Uptrends marks a big milestone; Multi-step API Monitoring has moved from beta testing to general availability! We've been putting Multi-step API Monitoring through rigorous testing first in private and then in public beta starting back in August 2017. We used feedback received from our beta test participants to help us further stabilize the monitor type along with the reporting. Although we will continue to add new features to Multi-step API Monitoring, it is already a fully realized, feature-rich monitor, and now Multi-step API is available to all of our Enterprise and Business plan subscribers.

    Multi-step API gives you the ability to verify complete API transactions from authentication through logoff with the ability to create dynamic variables for data reuse, use comparison operators, make assertions, and maintain and use client certificates. You will know your API or critical APIs you rely on work efficiently and correctly through the entire transaction. Multi-step API Monitoring is easy to set up, and it's ready for you now.

  • Enhanced Multi-step API dynamic variable supportNew

    In Multi-Step API monitoring, you can use the available automatic variables to generate dynamic data, including random GUIDs, random numbers, and dynamic dates and times. However, every time you use such a function in your request, it will generate a new value. What if you want to generate it once, and use that same value in multiple steps? You can now use automatic variables in your predefined variable definitions. Predefined variables are the variables that you define upfront and will be evaluated right before the multi-step scenario starts. The variables essentially become fixed values that are available throughout all steps in your scenario.

    Predefined Variables in Multi-step API Monitoring setup

    But that's not all! All variables (predefined variables, variables you define in individual steps, and even automatic variables) can now be used inside your assertions as well. This means that if you have an HTTP response and you want to check its content against a variable you defined earlier, you can do that. You can use a variable reference in an assertions' target value, or even include it as part of an XPath query or JSON expression.

    For more information, please read the Multi-Step API variables documentation.

April 2018

  • Single Sign-On public releaseNew

    Single Sign-On (SSO) for Uptrends lets you connect your Enterprise or third-party Identity Provider solution to Uptrends, giving your users a smooth and quick login experience without having to remember a separate password.

    The beta phase of this feature has been concluded, and SSO has reached general availability. This means that all Uptrends Enterprise accounts can now start using Single Sign-On. Read more about Single Sign-On for Uptrends.

  • Waterfall data and other details in APINew

    Uptrends API v4 exposes monitor data of individual monitor checks via the MonitorCheck API. This API gives you basic metrics that apply to any monitor check, but there is more detailed data available for checks of particular monitor types. The API now lets you access details of individual checks for HTTP-based monitors (HTTP headers and HTML content), Full Page Checks (waterfall data) and Transaction monitors (step details and waterfalls, when available).

  • Certificate metadata in VaultNew

    Certificate items stored in the Vault (full certificates uploaded as a Certificate Archive, as well as Public Keys) now show some certificate metadata (the certificate Issuer attribute, and the Valid From-Until attributes) when you inspect those items in the Vault. This metadata will help you to ensure you've uploaded the right certificate/public key.

  • Client certificates in Multi-step API monitorsNew

    Multi-step API monitors are now capable of sending client certificates: if you have an API that requires its users to identify themselves using a client certificate, you can now start monitoring your API. Upload your certificate to your Uptrends Vault and include the certificate in one or more API monitors. Read more about client certificates.

  • Storing sensitive data in your VaultNew

    Your Uptrends account now includes a new function called the Vault. The Vault helps you to manage usernames, passwords, certificates and other sensitive information you need as part of your monitor setup. It's a centralized way to stay organized, and to keep track of the different usernames you've set up for your monitors. Read more about the Vault.

March 2018

  • Firefox available for Full Page ChecksNew

    So far, Full Page Check (FPC) and Real Browser Check (RBC) monitors offered a choice between three browser types: Internet Explorer 11, Chrome and PhantomJS. We're now adding Firefox to this list!

    Each FPC or RBC monitor is configured to use one browser type. To monitor your web page performance in multiple browsers, you can create separate monitors that use the different browser types you are interested in.

  • Extra waterfall element: unused connectionNew

    Modern browsers spin up multiple connections with a web server to retrieve the elements of a web page as fast as possible. They do this because creating each connection takes time, especially when HTTPS is involved. Some of these connections are kept open for a while before an actual HTTP request is sent across that connection.

    This extra "unused" time wasn't displayed in waterfalls until now. Starting with Firefox FPCs, we're going to display that these connections are created early and only get used later on in the timeline. We're showing this extra timing aspect using a new element in the waterfall: unused connection.

    Introducing this element will give a more accurate representation of what actually happened in the browser. It will reveal that different browsers handle multiple connections in different ways.

  • Raw monitor check data download available via APINew

    A new function has been added to the Uptrends API v4 that lets you download the raw data for individual monitor checks. Once retrieved, that data can be stored in a database for offline analysis, or for audit or backup purposes. Learn more here.

February 2018

  • Dynamic date/time support for Multi-step API monitorsNew

    We've added a new option for generating dynamic content that can be used in Multi-step API requests: generating date- and/or time values based on the current date and time. Several formatting options are available (including Unix-style dates, ISO 8601 dates and custom formats) as well as offsetting for timezone adjustments and date calculations.

    Dynamic date/time values can be generated using the new @DateTime automatic variable. Full documentation is available in the Automatic variables section on this page.

January 2018

  • Protected Status PagesNew

    Public Status Pages have been around for a long time - they let you publish the status of your sites and services to the general public. But what if you want to publish that information to a selected group of people only?

    Introducing: Protected Status Pages. This new function gives you the flexibility of regular Public Status Pages, but lets you control who gets access. To learn more, visit the Knowledge Base article for Protected Status Pages.

  • Step duration in Multi-step API monitorsNew

    Multi-step API monitor data now includes the duration for each step: the dashboard for each API monitor features several tiles that show step duration progression over time, and averages for the periods you specify.