News & Updates

The Monitive Changelog

Tuesday, February 16, 2021
web v0.15.1 api v1.13.0

Introducing SMS Packages

As I mentioned last year, we’ll be providing unlimited SMS alerts to all customers at no extra cost, even though we pay for them, up to the end of January 2021. As the end of January arrived and we assessed the situation, it turned out that about a third of the subscription payment is going to Twilio, which is not feasible.

This is why, starting Monday, February 22nd 2021, we’re introducing SMS Packages, which are in packs of 200 SMS alerts.

There is nothing to do at this point. For easy transition towards SMS credits, you will automatically start with 200 credits on Monday morning UTC. As you receive SMS alerts and your credits decrease, you will get a low SMS notification once your credits reaches 30. And another one when you run out of SMS alert credits.

You’ll be able to acquire SMS Packages straight from your Monitive account with no profit margin for us.

To recharge your SMS credits, go to the Features & Apps screen -> SMS Alerts -> Recharge.

API Updates

  • feat: email notification before Altruistic plan expires (#426)
  • feat: send SMS announcement to users who use SMS alerts (#434)
  • fix: cannot log in with an updated email (#440)
  • fix: double-check doesn’t consider custom locations (#439)
  • fix: added $timeout & $tries for Quicktest Job and handled MaxAttemptsExceededException for Quicktest Job
  • chore: add team ID in the weekly report footer (#430)
  • chore: update quicktest settings
  • chore: update phone call alert offer

Tuesday, February 16, 2021
api v1.12.0

Maintenance Release: Timeout outage fix

FIXED: Some websites that went down by timing out did not trigger an outage.

This happened because the double-check procedure was taking more than 80 seconds, and was therefore killed due to timing out. This caused some outages caused by timeouts to be missed.

This is now fixed so any monitored service that times out should now properly trigger and outage and dispatch alerts as configured.

API updates

  • feat: quicktest feature (#411 #423 #425)
  • feat: SmsMessage Component (#417)
  • chore: return joinedTeam attribute with registration response (#412)

Thursday, February 4, 2021
web 0.15.0 api v1.11.0
PDF Reports

PDF Reports

You can now generate custom PDF reports that you can download, archive or send to your auditor and customers.

Next to the HTML button in the Reports listing, you now have a PDF button that will open the equivalent report in PDF format.

Other improvements and fixes

  • feat: add PDF button to reports that have a PDF variant (#120)
  • feat: add powered by stripe and wire transfer info (#119)
  • chore: convert tracking from GA to GTM dataLayer
  • chore: remove NProgress for now

API updates

  • feat: PDF generation for custom reports (#369)
  • chore: updated dependencies (#401)
  • chore: removed unused file imports (#405)
  • docs: swagger API Calls Docs Update (#388)
  • fix: incorrect year is being displayed in the subject of Monthly reports (#409)
  • fix: sending delayed alerts when monitor is disabled (#406)
  • update Tax ID countries with the missing 8 (fixes #393)
  • chore: updated dependencies (#391)

Wednesday, January 27, 2021
web v0.14.0
Enable or disable monitors from the list

Enable or disable monitors from the list

A useful UX improvement is the ability to enable or disable monitors directly from the monitors list, on landscape tablets and desktop. This way, when you need to disable or enable several monitors, it’s just a matter of click-click-click-click and you’re done.

Also added nice tooltips to the actions to make it clear on what each one does.


Wednesday, January 20, 2021
web v0.13.0
New Help screen and monitoring locations list

New Help screen and monitoring locations list

The Help screen has been redone, in a more useful and organized manner.

Added the monitoring locations list, so if you have any firewalls set up and you want to whitelist Monitive IPs to be able to check your services, this list included IP, location and current status (enabled or not).

The Feedback Forum & Report a Bug links in the Account menu are now sections in the Help screen.

You’ll also find ways to get in touch with us, via Whatsapp, Telegram or email.

We hope you find the Help screen helpful, and if you have any suggestions on how to further improve it, please let us know.

Other improvements and fixes

  • update onboarding screens (#113)
  • chore: remove monitive classic support (#117)

Saturday, January 16, 2021
web 0.12.1 api v1.10.1
Refresh PagerDuty Integration

Refresh PagerDuty Integration

We had a loophole in the PagerDuty integration, where if you added more services in PagerDuty after connecting it to Monitive, you couldn’t bring in the new PagerDuty services without loosing the configuration.

Now you can go to the PagerDuty integration screen and click Refresh Connection to go through the authorization again and get the new services into Monitive.

Other improvements and fixes

  • fix: “Check you text” typo
  • chore: Spanish translations update (#89)
  • chore(deps): bump axios from 0.18.1 to 0.21.1 (#106)

API updates

  • feat: add ability to refresh feature settings (#384)
  • feat: create incident when firstState is DOWN (#365)
  • feat: automatic review invitation (#371)
  • feat: aggregate a list of user’s domains (#380)
  • fix: WopherRequestFailedException to handle failure and turn off location (#361)
  • fix: Serialization of ‘Closure’ is not allowed (#376)
  • fix: negative team availability (#382)
  • chore: updated dependencies (#367)
  • chore: remove package.json
  • docs: added wopher setup instructions (#381)

Wednesday, December 30, 2020
web 0.11.0 api v1.9.0
Custom Uptime Reports

Custom Uptime Reports

You can no create customized uptime reports, for any set of monitors and any particular time frame.

Enable the Custom Reports feature from your Features & Apps screen to enable access to previously sent weekly and monthly reports, and to be able to generate new, custom reports.

Other improvements and fixes

  • feat: new feature: Custom Reports (#102)
  • feat: show API error message when re-inviting an existing invited user
  • feat: members cannot manage features
  • feat: hide Subscription from team members
  • feat: explain account delete
  • feat: revoke invitation and remove user confirm (#101)
  • docs: add PagerDuty instructions link
  • fix: style the new feature popup
  • chore: comment out unused call
  • chore: finalize custom reports (#105)

API updates

  • feat: implement new Custom Reports feature (#362)
  • feat: deny subscription-related requests to member users (#360)
  • feat: attach user when inviting user with no team (#354)
  • feat: phone clearing side-effects (#364)
  • test: rename file to be according to class
  • fix: undefined index: w8-sg-lnd in Workload (#363)
  • chore: enable custom-reports feature

Wednesday, December 16, 2020
web 0.10.0 api v1.8.1
Weekly and Monthly Reporting Preferences

Weekly and Monthly Reporting Preferences

Each week we’re sending an uptime report to the team owner with the previous week statistics including uptime, downtime and response time.

We’re doing the same every month on the 1st, for the previous month.

If you don’t need these, you can now disable them in your User Profile screen. They’re enabled by default, so if you want these, there’s nothing to do.

Other improvements and fixes

  • feat: add weekly/monthly reports support
  • feat: allow phone number update/removal
  • fix: handle user with no team
  • fix: only update attributes that have been modified

API updates

  • feat: only add owner users to marketing onboarding (#344)
  • feat: don’t list invitations that have already been redeemed (#343)
  • feat: weekly / monthly report user preferences (#342)

Monday, December 14, 2020
web 0.9.5 api v1.6.1
Team Management policy updates

Team Management policy updates

Whenever there’s a team involved, things can easily go south.

This is a policy update with improvements on how a team is managed plus various fixes and updates to increase the system’s stability.

API updates

  • feat: added team-management remove handler (#340)
  • feat: enable Maintenance Window feature
  • feat: revoke team invitation, team users should not be able to remove team owner (#335)
  • feat: team member cannot enable/disable features (#338)
  • feat: deny removal of team-management feature if users still have access (#336)
  • chore: upgrade packages & lock PHP version on CI test suite (#341)
  • chore: handle no locations situation
  • chore: use constants for Wopher timeouts

Friday, December 11, 2020
web 0.9.5 api v1.5.0
New: Maintenance Window feature

New: Maintenance Window feature

Sometimes, downtime is intentional, even for Internet services. With the new Maintenance Window feature, you can set a time frame for any monitor, when you know you have maintenance work and it is likely to go down.

The maintenance time frame can be either daily, between certain times, or on a specific date and time.

Other improvements and fixes

  • feat: new feature Maintenance Window (#90)
  • feat: add ID to sign in form elements
  • fix: don’t duplicate alert-rules user on monitor save
  • fix: notify Bugsnag when importing fails
  • fix: use alert-rules rules only when enabled
  • docs: update maintenance window docs
  • fix: only load/dispatch load if we have an ID (#97)

API updates

  • feat: maintenance Window feature (#327)
  • feat: migrate TCP Port for Classic users (#334)
  • feat: enable Webhook channel and Team Management
  • fix: send monitor created event after migration

Thursday, December 10, 2020
web 0.8.1 api v1.4.2
TCP Port monitoring, Team Management, PagerDuty & Webhooks

TCP Port monitoring, Team Management, PagerDuty & Webhooks

Major update adding four new features to the new Monitive.

  • TCP Port Monitoring - monitor any public host/ip device in the world that accepts TCP connection on a port.
  • Team Management - invite users to your team, configure who to alert and when, for each individual monitor.
  • PagerDuty Integration - trigger events in your PagerDuty services whenever a monitored service goes down. See integration instructions for more details.
  • Webhooks - formerly known as HTTP POST Alerts, this feature allows you to configure an URL that we’ll HTTP POST to when a service is going down.

Other improvements and fixes

  • feat: New Webhook feature (#79)
  • feat: manage users screen (#52)
  • feat: TCP Port Monitoring (#84)
  • feat: PagerDuty integration (#81)
  • feat: allow multiple users on each alert rule
  • feat: specify service type in Classic migration list
  • fix: replace all tags & ensure textContent is string (#96)
  • fix: chunk load error (#93)
  • chore: update TCP port monitor description
  • docs: add Webhook feature description
  • fix: don’t show team management
  • docs: add Team Management feature intro & docs
  • fix: disable non free alert channels (#80)
  • set proper .gitattributes
  • update apple-touch-icon.png
  • update packages
  • fix: mobile monitors list to use new edit monitor
  • fix: account edit news fixes (#86)
  • add alert user validation
  • fix: replace all tags & ensure textContent is string (#96)

API updates

  • v1.4.2 Enable PagerDuty and TCP Port for the public
  • v1.4.1 CI force-seed Channels on deploy
  • v1.4.0 Webhooks, TCP Port, PagerDuty, Team Management
  • feat: add tcp_port check results support (#312)
  • feat: Webhook / HTTP POST Alert (#303)
  • feat: new PagerDuty integration (#318)
  • feat: invite a user to a team, list team users (existing and invited), deletes a team member (#147)
  • add rollback instructions
  • fix: release errors via Sprinkler missing interval (#311)
  • fix: update dispatching of down monitors (#313)
  • fix: remove Webhook channel alert rules when deactivating feature
  • fix: explicitly request ubuntu-18.04 (#316)
  • fix: handle tcp-port line-protocol entries
  • chore: renamed TcpportCheck class to TcpPortCheck (#315)
  • chore: add outlook email to beta users
  • chore: log to New Relic
  • chore: remove bugsnag (#330)
  • chore: set sprinkler skipping to debug

Wednesday, December 2, 2020
api v1.3.1
Check down monitors every minute

Check down monitors every minute

When you have the Custom Interval monitoring feature enabled, you can set your monitors to be monitored every 1, 5, 30 minutes or even 6 or 24 hours. But when such a monitored service goes down, if it’s not checked more often, you were getting inaccurate downtime information.

For example if we’re checking it every 30 minutes, and it goes down, we’ll check back in 30 minutes if it’s back up, even if it might have been just a 2 minutes outage.

We changed this so now when a monitor that has a > 1 minute interval is down, we’re checking it every minute until it’s back up. Then we’ll resume our normal checking schedule.

Other improvements and fixes

  • fix: alert rule channel ID validation of string IDs (#299)
  • chore: deactivate sending the second email confirmation notification (#307)

Tuesday, December 1, 2020
web v0.6.1
In-app news and updates

In-app news and updates

Since the news and updates page (formerly Changelog) is now up-to-date with everything that happens around the new Monitive, we’re also displaying the latest news in the Monitive web-app.

Whenever there’s something new, a thin alert will be displayed at the top of the interface, only on Desktop. In case you missed it, you can also see the last 5 updates on the Dashboard screen.

Other improvements and fixes

  • fix: properly display news description

Wednesday, November 25, 2020
web v0.5.1 api v1.3.0
PING Monitoring

PING Monitoring

PING Monitoring is now available for all Monitive Pro users, allowing you to easily monitor any Internet device that is reachable via PING.

Other improvements and fixes

  • add New Relic
  • fix: migration “Importing” message
  • fix: grouped latency factor / 1000

API updates

  • feat: verify email address at registration time (#287)
  • feat: enable ping for all users
  • feat: delete unconfirmed accounts after 3.5 days (#295)
  • chore: updated dependencies (#290)
  • fix: convert migrated ping timing to nanoseconds (#291)
  • chore: updated dependencies (#273)
  • chore: Show number of active subscriptions in the Daily Scoop (#280)
  • fix: Kohana monitors don’t have response_time5
  • fix: allow ping monitors to be migrated (#285)
  • fix: Kohana import date format
  • fix: validate date_modified and fallback to created
  • fix: create settings based on monitor type
  • fix: ping uptime reports & perfect week/month reports title (#281)
  • fix: Stripe\Exception\InvalidRequestException for non eu_vat tax ids (#286)
  • fix: ConfirmMonitor Trying to get property ‘id’ of non-object
  • fix: don’t log exception when ConfirmMonitor can’t lock (#279)

Monday, November 16, 2020
web v0.4.0 api v1.1.0
Six new HTTP features released

Six new HTTP features released

New HTTP monitoring features released today, wrapping up pretty much all the HTTP requirements for a powerful, flexible yet simple monitoring solution for HTTP and HTTPS monitoring. The following are now available:

  • HTTP Custom Status (such as 401, 404 etc.)
  • HTTP Custom Status monitoring (such as 404 or any other)
  • HTTP Custom Headers
  • HTTP Custom Method (such as POST, PUT, PATCH, DELETE etc.) + body payload to send
  • Custom Timeout (1 to 30 seconds)
  • Custom Interval (1 minute to 24 hours)
  • Custom Locations

This allows you to monitor a plethora of HTTP services, from simple pages to API authentication requests or pretty much anything you might need.

New features

  • feat: Custom Locations feature (#64)
  • feat: add service type to mobile monitor card
  • feat: optimize mobile list loading
  • feat: compact monitor list header actions (mobile)
  • feat: Mobile compact monitors list (#69)
  • feat: show 25 monitors per page
  • feat: Custom Interval feature (#63)
  • feat: add custom timeout (#62)
  • feat: HTTP Custom Headers (#58)
  • feat: HTTP Custom Method (#56)
  • feat: Custom HTTP status feature (#46)
  • feat: add HTTP Status instructions
  • feat: show all features as coming soon if not available

Other improvements and fixes

  • fix: custom edit issues & simplify edit dialog (#68)
  • fix: add ping into
  • fix: null when we don’t have headers
  • fix: small chip on group tag (#70)
  • fix: don’t start Bugsnag if we don’t have a key
  • fix: show precision and scale according to service type
  • fix overall latency chart
  • fix: test without status code
  • fix: second fixing attempt
  • update cloudflare serving
  • don’t cache index.html
  • fix: Basic Auth copy
  • upgrade to Vue 2.3.14
  • chore: upgrade JS packages (#44)
  • docs: add useful resources
  • add event tracking and fix some issues (#48)

API updates

  • feat: enable new features for the public (#278)
  • feat: don’t allow Free plan users to save a monitor with non-email alert rules (#272)
  • feat: added TLSHandshake to results (metric9) (#225)
  • feat: custom check locations (#227)
  • feat: disable non-email alert rules for downgraded users (#247)
  • feat: retrieve a monitor’s custom locations (#250)
  • feat: remove HTTP Custom Status on feature deactivation (#258)
  • feat: reduce minimum timeout to 1 second (#263)
  • feat: feature removal listener handler for all implemented features (#262)
  • feat: mention free sms call alerts (#182)
  • feat: send failed jobs to Bugsnag (#183)
  • feat: added Ametrine bonus (#186)
  • fix: misleading Dispatching errors by Sprinkler (#277)
  • chore: updated dependencies (#268)
  • fix: add type tag when updating missing (#264)
  • chore: upgrade LineProtocol to handle measure9 (#198)
  • chore: updated dependencies (#217)
  • updated dependencies (#234)
  • fix: statusCode should be coming as numeric (#235)
  • fix: convert PING metrics to be usable (#223)
  • fix: validation error for /data/attributes/settings/statusCode & data.attributes.settings.keywordBody (#241)
  • fix: downgrade to free time fix (#242)
  • fix: set Ping metric1 as Average RTT (#244)
  • fix: all upgraded users are downgraded after the trial period (#248)
  • chore: updated dependencies (#257)
  • fix: changed Sprinkler runtime to 65s to fix AltThree\Locker\Exceptions\UnableToAcquireLockException (#206)
  • docs : added a view for the list of rendered emails for dev environment (#200)
  • chore: updated dependencies (#193)
  • fix: updated CTA in the trial expiration emails (#195)
  • chore: extended Sprinkler runtime to 90 seconds (#196)
  • chore: added generic BCC of Mailables being sent to customers (#197)
  • fix: phone number sender issue to +14******064 (#199)
  • fix: Sprinkler dispatching too many monitors per location (#180)
  • fix: configured custom $tries, $timeout for Jobs\Sprinkler (#181)
  • fix: update the “Sprinkler has no monitor to check for a specific interval” to info level.

Tuesday, October 13, 2020
web v0.2.5 api v0.9.5
Test monitor before save

Test monitor before save

Isn’t it frustrating to add a monitor just to see that your settings weren’t right and it will immediately be reported as down?

This feel like starting off on the wrong foot with either a new or even an older monitor, since the outage caused by the mismatched settings will go down in history.

The solution to this is a very useful Test button just next to the Save button which does exactly that: Checks the current monitor settings without updating them.

Other improvements and fixes

  • New: Show link to monitor URL.
  • New: Add support for adding PING monitors (beta).
  • New: Show a user if he’s on the free trial period and how many days he has left.
  • New: Show a warning if trying to add a monitor when account is at maximum monitors for the current plan.
  • New: Show if there’s a bonus available on the Plan page.

API updates

  • New: added ‘custom_check’ to ‘beta_only’ team features (#161)
  • Fix: remove sprinkler status check (#159)
  • Fix: restart PHP 7.3 after deploy
  • Fix: ping service outage/recovery alerts not send (#174)
  • Fix: enable testing and checking of the ping service type (#166)
  • Chore: update dependencies (#154)
  • Chore: updated Horizon assets by running php artisan horizon:publish (#155)
  • Chore: update dependencies (#173)
  • Chore: rename team features and add handlers (#164)
  • Refactor: Removed return statement from TeamsMonitorsController@all (#138)
  • Refactor: Changed Sprinkler console command to a scheduled task (#126)

Friday, August 28, 2020
web v0.2.0 api v0.9.0
Pronounceable name

Pronounceable name

This is a new feature for the monitors with names that are just unpronounceable in the English language, you can now set a pronounceable name. This way you will be sure you’ll understand right away what’s the outage alert phone call about.

Edit any monitor and scroll down to the Pronounceable Name input field to add a pronounceable name.

If you leave it empty, we’ll just use the monitor’s name.

Other improvements and fixes

  • Enabled the language selector (#31)
  • Added subscriptions and payments support (#5)
  • Detect and set country & timezone via CloudFlare and JS (#26)
  • Fixed: send proper ?include=team when deleting (#3)
  • Fixed: show Stripe error message if we receive one (#29)
  • Fixed: display VAT ID if user previously saved it (#28)
  • Fixed: show card saving feedback and allow user to update card (#27)
  • Fixed: adjust translations and styling for the feature cards
  • Fixed: align back arrow with title on secondary titles
  • Fixed: add/edit monitor dialog was confusing New vs Add
  • Fixed: show interface when refreshing the page in the Help section
  • Fixed: set password validation (#32)

API updates

  • Remove previous tax IDs when updating customer billing info
  • Add altruistic plan and get the actual plan a team is on
  • Added status_code setting to http Monitors
  • Generate user access token for technical support
  • Coupon support for teams
  • Manage bonuses
  • Fixed: don’t report authentication failures in the logs.

Tuesday, August 4, 2020
Spanish Monitive homepage

Spanish Monitive homepage

To better address our customers, we now have a Spanish version of the homepage, and we’re working on translating the web app as well.

Other improvements and fixes

  • Updated the GeoIP JS used preselect the country dropdown on Sign Up.
  • Fixed a sign-in issue showing “Something went wrong” instead of “Incorrect email or password”

API v0.8.9 Released

  • Migrated API backend from Lumen to Laravel.
  • add pronounceable attribute to the monitors, using it for call alerts pronounciation.

Sunday, June 21, 2020

Migration Issue Fixed

There was a major issues that prevented Classic Monitive customers that created their accounts in the new platform after the launch to migrate their monitors into the new platform. This is now fixed.

Other improvements and fixes

  • Added redirect to Monitive Classic status pages.
  • Fixed a logging issue with Mailchimp’s event sending.
  • Added Sign in link on Monitive’s homepage header.

Thursday, June 18, 2020
Montive `Freyja` Official Launch

Montive `Freyja` Official Launch

Today we launched the new Monitive on Product Hunt. This is the core of an uptime monitoring service that will aim at crafting a better Internet - one site at a time. There are a lot of great updates coming up in the next months and we’re excited to get your feedback on the new Monitive, so please add your suggestions or feedback in the Feedback Forum.

Other improvements and fixes

  • Changed response time measurement from milliseconds to seconds.
  • Added “Last 30 Days” above the Uptime and Response time charts.
  • Changed the monitive.com homepage with the new Monitive.
  • Moved the old monitive homepage to classic.monitive.com.
  • Added onboarding screens for accounts less than 7 days old.
  • Added links in the new homepage’s footer to Monitive Classic Homepage and Monitive Classic Admin account.

Thursday, June 4, 2020
Migration Tool from Monitive Classic accounts

Migration Tool from Monitive Classic accounts

You can now import your old Monitive Classic monitors including availability & latency history into your account.

Other improvements and fixes

  • Updated the mobile bottom navigation bar and fixed navigation bar height / position in mobile full-screen mode.
  • Fixed weekly & monthly uptime report - overall availability percentage, it was not taking into account the number of monitors, resulting in lower than actual availability %.
  • Fixed report heading when the availability was 100%.

Friday, May 22, 2020

Articulated call alerts via Amazon Polly

Each time I got an outage alert call, I was not impressed about the syntetic voice that told me that my website was down. Long story short, we’re now using Amazon Polly to generate naturally-sounding alert calls using Joanna’s Neural voice.

Other improvements and fixes

  • Fixed desktop Incidents table in the View Monitor page not showing duration nor outage end date/time;
  • Updated the duration in all the outages display to a human-readable format (hours, minutes, seconds);
  • Updated the reports header to be consistent with the brand;

Friday, April 24, 2020
Group Monitors

Group Monitors

When grouping is enabled, monitors are sorted by groups (ungrouped first), and then alphabetical, to make it easier to skim through the list of monitors. You also get aggregated availability and response time for each group of monitors.

If you want it, just head out to Features & Apps in your Account / Profile menu, and enabled it. After that, on the edit / add monitor page you can create or select a group.

Other improvements and fixes

  • The Features & Apps page has been polished.
  • Various card styling was updated for consistency.
  • The edit / delete icons in the desktop list of monitors were too small.
  • Phone call outage alerts were enabled for the following countries: Mexico, Spain, Portugal, Denmark, Switzerland, Malaysia, Thailand;

Friday, April 10, 2020
Mobile Progressive Web App (PWA)

Mobile Progressive Web App (PWA)

The Monitive web app is built as a Progressive Web App, meaning you can add it to your homescreen on Android and iOS and it will behave like a fullscreen native app. The advantage is that you’re always logged in, it automatically refreshes when an update is available and it is going to be packaged in mobile app that will be available in the App Store / Play Store later this year.

Other improvements and fixes

  • User profile could not be updated when the signup email was longer than 30 characters.
  • The UK flag was missing in the Recent Checks card.
  • Phone call alerts to Mexico failed due to Twilio Geo permissions mismatch.
  • PWA refresh was broken.

Top