Recent changes in Uptrends

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

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.

December 2017

  • SLA uptime% for new subaccounts had an incorrect valueFix

    Enterprise users who are using the Sub accounts feature may have noticed this problem: when a new sub account was created, the default values in the sub account's SLA settings were incorrect: the uptime percentage settings in the SLA (used to specify which percentage is still acceptable, and which percentage should lead to a warning or error indication in the SLA reporting) got a really weird value after the sub account was first saved.

    We've fixed this now: the default uptime percentages are set to 99.0% (anything below this value will show up as a red error) and 99.90% (this value or higher shows up as OK, anything in between shows up as a yellow warning).

  • Menu item to buy extrasChange

    Depending on your account type, it's possible to purchase additional resources in your account: extra monitors, extra operators (user logins), extra message credits for SMS and phone alerts, or the option to start using Real User Monitoring.

    It wasn't very clear to all customers that those options are available: account administrators can now purchase all these extras by choosing Buy extras in the Account menu.

    Some pricing plans have a limited option for buying extras. If you are looking to extend your account if you need more monitors, operators or alert definitions, please contact Support so we can discuss upgrade possibilities.

  • Multi-step API authentication supportNew

    Support for Basic authentication, Digest authentication and NTLM (Windows) authentication has been added to Multi-step API monitoring. You can add authentication settings to each individual step (or just one, if that's what you need). For more information about authentication on HTTP level, or for setting up OAuth-based authentication, please read our documentation on multi-step API authentication.

    Please note that authentication capabilities for API monitoring is currently being rolled out across our network. For more information about this process, please read this article about the API monitoring beta conditions.

  • Ignoring TLS certificate errorsNew

    As part of our regular monitoring, each HTTPS URL you specify is checked for a valid security certificate. We'll check that the certificate hasn't expired, that the certificate actually applies to the domain you specified, and that the certificate authority who signed the certificate can be trusted.

    There may be specific circumstances where you want to ignore certificate problems, and continue monitoring anyway. We've added a new option for multi-step API monitors called "Ignore TLS/SSL certificate errors", which lets you bypass the certificate validation.

  • SMS gateway settings available to all usersFix

    In order to send SMS alerts to our customers, we use several different SMS gateways that operate in different parts of the world. Your team members may be located in different countries, so each user should be able to choose the appropriate SMS gateway for the best message delivery to their phone.

    Even though administrator users could already do this for their teams, we're now empowering each user, including non-administrator users, to change this in their own user settings.

November 2017

  • Automatic variables in Multi-step API monitoringNew

    We've added a number of automatic variables for multi-step API monitors that can be helpful for generating data in your requests.

    Read all about it in the Multi-step documentation on variables.

  • Multi-step API monitoring in public betaNew

    We're introducing a new monitor type: Multi-step API monitoring. This monitor type is currently in beta. Read more about its functions here.

  • Alerting reminder intervalChange

    When you're configuring your alerting settings, you can specify how often you would like to receive reminder alerts. The interval between consecutive reminders was previously limited to 500 minutes, but this limit has been lifted. This allows you to use longer interval settings. For example, fill in '1440' (24 x 60) to set the interval to a day.

October 2017

  • StatusHub integrationNew

    We've added a new integration option: you can now integrate your Uptrends monitors with the services in your StatusHub account.

    StatusHub uses the traffic light system to publish the status of your sites, APIs and services to the general public. Uptrends can control those traffic light values automatically so your audience is always up to speed about the status of your services.

    Please visit the StatusHub integration guide for more information.

  • Applying monitor templates didn't always workFix

    We recently introduced a problem in the way that monitor templates work: the process of applying a monitor template to one or more existing monitors appeared to hang, which effectively made it impossible to apply the required changes to those monitors.

    We've made this less problematic by... fixing that bug . Applying a monitor template should no longer cause any problems now. For more information on how to use templates to bulk update your monitors, please visit the knowledge base article about monitor templates.

September 2017

  • Real User Monitoring is out of beta! New

    Uptrends’ RUM is fresh from beta testing and ready for you to try free for 30 days. Real User Monitoring (RUM) brings you performance insights directly from your users’ experience.

    If you want to learn more, pay this page a visit.

    Need help getting started? Check out this Knowledge Base article.

August 2017

  • Updated list of user agentsImprovement

    We've updated the list of user agents for HTTP(S), Real Browser Check and Full Page Check monitors. A user agent string is a value that identifies a particular browser type and version. That value will be sent across as part of the HTTP requests generated by your monitors. When you configure your monitors, we'll show you a list of the latest versions of the most common browsers, but you can also specify your own.

    Keep in mind that it's just a text value: it doesn't mean that HTTP(S) monitors run in an actual browser, nor does it change the type of browser we use to run your RBC and FPC monitors. Still, the user agent value may be used by your server application to change its behavior according to a certain browser or device platform.

    Even though we've updated the list of default user agents, existing values representing older browser versions will continue to work.

  • Monitor list export shows number of transaction stepsImprovement

    Transaction monitors execute a number of steps as part of a web browser scenario. Longer transactions with more steps take up more space than shorter transactions.

    Some Uptrends users asked for an overview of this transaction cost. If you use the export function (for Excel or PDF) in the Monitors list, you'll get an extra column that shows the monitor cost for each transaction. In fact, it will show the appropriate cost for other monitor types as well, so it should add up nicely to the number of monitors you are currently using.

  • Waterfall chart filter is no longer case sensitiveFix

    For Full Page Check (FPC) and transaction monitors, we track all requests and web resources downloaded by the browser. The timing info for each request, along with every HTTP request/response detail, is displayed in a waterfall chart. The list of requests can get pretty long, so there's a filter box you can use to quickly narrow down that list.

    However, the filter function wouldn't find the correct items unless you typed lowercase and uppercase letters exactly like it was in the requests we tracked. There's really no need to be that picky, so we've fixed that.

  • RUM data is now sortableImprovement

    All RUM grids that show data for pages, device types, countries, browsers and operating systems can now be sorted. By default, each list is sorted by number of page views (high to low), but the tile settings for each grid include a new option that lets you select any metric to sort by.

    For example, select Sort by Load time in the Pages list to find out which page is the slowest to load. Using the same metric in the Countries list shows you which country is experiencing the longest load times.

  • Created and last modified fields in the monitor listNew

    The list of monitor definitions now shows you the date and time a monitor was created (when available) and when it was last modified. This information is also included in the Excel export for that dashboard so you can do further analysis and sorting.

  • Starter accounts get the monitor status dashboardNew

    Good news for Starter account users: you have a new dashboard! The Monitor Status dashboard shows the current status of all your monitors (it refreshes automatically), along with the time and checkpoint location of the last check, the total load time for that check, and some handy switches for toggling your monitor and alerting activity.

    For Premium, Professional, Business and Enterprise customers: you already had this dashboard, and we'll never take it away from you.

July 2017

  • Changing monitor passwordsImprovement

    We've changed the way you can update passwords in your monitor settings. If your monitors require authentication, specifying user names and passwords for new monitors still works the same. Once they've been saved in your settings, you need to explicitly choose the Edit function for the password if you want to change it. When you've made a change, either save your updated settings like normal using the Save button, or choose Cancel edit to leave the password unchanged.

    Changing a password in a monitor's settings

  • Timezones in support ticket overviewFix

    The support ticket overview shows on which date/time your support tickets were created and last updated. These times were displayed in the UTC timezone, not the timezone specified in your account. This has been corrected.

  • Return password value in APIFix

    When you specify usernames/passwords in your monitor settings (we support Basic, Digest and NTLM authentication... and more to come soon!) we store those values securely. However, when you retrieved monitor settings through the Uptrends API, the original password was also returned. This was definitely an unnecessary exposure of the password, so we've changed that. The password field is still part of the API definition, but it will no longer return any sensitive values.

  • URLs in DNS report toolFix

    It was discovered that our DNS report tool choked on URLs that contain non-ASCII characters such as diaeresis/umlauts. Some surgery was performed, and now it eats äüöï for breakfast.

June 2017

  • Export of unconfirmed errors in "Errors overview" dashboard Fix

    The errors overview dashboard contains a convenient breakdown of the types of errors. We'll show you how many of those errors were confirmed, and how many were unconfirmed. If you ran an Excel or PDF export of that list, we showed you the unconfirmed numbers twice. That's a bit much. Fixed it!

  • Send a test SMS without saving your phone numberFix

    If you rely on SMS messages to receive alerts from Uptrends, you probably want to test if we can send alerts to your phone. You can do that in your own operator settings (click on your name at the top right to get there). We made this way too hard for users who are not administrators - they had to save their mobile phone number first before receiving a test message. Silly bug that has been fixed now.

    Operator settings Test SMS

  • Unnecessary link in ticket confirmation screenFix

    When you've filed a ticket for our Support engineers (they love to hear from you, send in your ideas!) we show you a quick confirmation screen with the ID of the new ticket. It also contained an unnecessary link that made some people send in the same ticket again. No more confusing links, we promise.

April 2017

  • Direct link to monitor check also preselects date and monitor filterImprovement

    Alert e-mails, Slack alerts, and the alert detail popup contain direct links to the monitor check that caused the corresponding alert. When you click the link, we'll display a popup with the appropriate check details, and the monitor log dashboard gets loaded in the background.

    What's new in this update is that we'll now automatically apply a filter to the monitor log: we'll pre-select the date/time window in which the check happened and we will only display checks for the appropriate monitor. As soon as you escape out of the monitor check details popup, you can quickly review any checks that happened before and after the start of the alert.

    Check Detail URLs now preload the dashboard filtered based on the incident.

  • Error documentation available in French, German and DutchNew

    We recently added links to error documentation for individual errors in the monitor check detail popup and alert detail. Previously only available in English, the documentation is now available in the other languages as well.

March 2017

  • Tighten up your reporting periodImprovement

    We’ve reworked the reporting period selection tool to make it easier to use, and we took it a step further, you can now pick the hour for your reporting period! Because you're able to narrow down the period, you can find a specific error or zoom in on a specific time range much easier. We've also added more flexibility in the available options in the period selector.

  • Dig in deep with chart drill downsNew

    Have you ever found yourself looking at a spike in a bar or line chart and wished you could just jump to the details directly? Well, so did we, and we did something about it. Now when you see something that piques your interest on a chart, you can simply click on the line or bar chart and we'll take you to that specific period in your monitor log, when the event took place.

  • Error descriptions a human can understandImprovement

    Yeah, we admit it; Uptrends’ error descriptions have always been a bit hard to grasp. However, we’ve changed that, a lot! We’ve gone through every error code and given them easy to understand descriptions. If that wasn’t already reason to celebrate, we went further; if you need more information about the error code, click the link right next to the error description to see the detailed description in the Knowledge Base.

    We’ve wanted to improve and expand this page in the Knowledge Base for a long time, so since we were already there, we added a search feature. A quick search gets you to the information fast.

  • Share the misery, uh... we mean error detailsImprovement

    Do you need to get the error details to your team out fast? Now you can! Every check in your monitor log is now shareable, by just copying the URL in your browser window. The URL opens the specific log detail in your monitor log. Just copy and send; it is that easy!

    After adding the URL to every log entry, we got to thinking; why not send the URL with your alerts? So, we do. Now you can see the monitor log detail immediately by just clicking the URL in your alert email or Slack messages.

  • New tile types New

    It's now possible to add the "Last Full Page Check details", "Full Page Check grid" and "Full Page Check Timing chart" tiles to your own custom dashboards.

  • "Use only primary checkpoints" in monitor templatesImprovement

    Recently, we added the "Use only primary checkpoints" option in the checkpoint selector for a monitor. We've now included this option in monitor templates as well.

  • PSP drilldown did not work inside iframeFix

    Some customers who publish their Public Status Page put that PSP in a frame within one of their own pages (see our demo page at to see how that looks). In those cases, it was not possible to click on one of the monitors in that PSP to navigate to the corresponding details.

February 2017

  • Easily spot blocked waterfall requests Improvement

    A Full Page Check monitor loads a web page in a browser, and loads all the elements that are part of that page - including Google Analytics scripts and other third party elements that are part of the page. In doing so, the pages loaded in our browser are triggering genuine pageviews in your web analytics. If this is skewing your analytics too much, or if there's another reason you don't want particular third party elements to be loaded, there are two ways in the FPC's settings to control this: The Block Google Analytics option, and the Block these URLs option which, you guessed it, allows you to block particular URLs.

    When you look at the check results and open up the waterfall chart, you'll still see the corresponding requests. Why is that?

    Well, we can't simply tell the browser not to load those URLs. Instead, we bypass those requests as soon as we see them, and prevent them from going out onto the internet. Google Analytics will never see those requests, so your analytics are now safe. The browser still needs an answer for those requests though - the only thing we can do is return an empty response. Your web page may or may not break as a result of this.

    To show you which requests were bypassed and essentially blocked, and when that happened during the page life cycle, we're still showing them as part of the waterfall. Blocked requests will appear as strikethrough, so you can easily spot them. This tells you exactly which requests were intercepted based on our Block settings.

  • Extra filter for Native IPv6 locations Improvement

    For basic monitor types, you can specify whether you want to use IPv4 or IPv6 to perform that test. Most of our checkpoints currently support IPv6, but not all checkpoints do so natively. In those cases, we offer IPv6 over IPv4. In some cases, you may want to run your monitors only on checkpoints that have native IPv6 and skip the ones that only offer IPv6 over IPv4. To do this, you can now choose the "Native IPv6 only" option.

  • Slack integration changeChange

    The Slack integration change that was announced in the release notes of February 1st is now in effect.

    Please refer to the Slack integration page to see the current steps required to set up a Slack integration. If you have any questions regarding this change, please file a support ticket

  • Slack integration changeAnnouncement

    Unfortunately, Slack no longer allows us to post to channels other than the ones you explicitly specified during the integration setup. This is why we have to retire the option of specifying any channel names in an escalation level. We will do so on February 15, 2017.

    As a result, some action is required on your side by reconfiguring your integrations. Our advice is to re-create separate Slack integrations (via the Alerts > Integrations menu) for each Slack channel you would like to post us to, and link the appropriate escalation levels to those new integrations. Please note that you can define as many Slack integrations as you need. Until you do so, your existing integrations will remain as-is, and we will continue to post messages to the default channel for each integration.

    Please refer to the Slack integration page to see the current steps required to set up a Slack integration. If you have any questions regarding this change, please file a support ticket