Recent changes in Uptrends

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

August 2017

  • 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 peaks 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 https://galacticresorts.com/status 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