Changelog

This has been long due: ability to send alerts to arbitrary emails. Until now, you had to enable the Team Management feature, and to create users for each email address that you want to send alerts to.

No more. Now, just head out to the Recipients screen and add as many Email alert recipients you need to.

You can also send test alerts to your email recipients, to see how they look like:

And, last but not least, you can now edit any monitor and select any or all of the email recipients you previously created:

Admin updates

• Added new Email* channel (#213)
• Added plan pricing and benefits on the Get Started screen at app.monitive.com (#227 #229)
• Changed join team sign-up screen, removing the phone number requirement
• Fixed issue preventing free users from enabling email alerts (#233)

API updates

• Added sync user recipients console commands, allowing us to sync recipients on all teams & users (#629)
• Added email channel signup and downgrade support, to not remove the email channel (#622)
• Changed Email New to Email* (#632)
• Security update of packages & dependencies (#625)

We revamped the availability charts you're seeing for each monitor. You can now spot patterns when you're looking at a monitor's availability.

The chart card has 3 views, one for the last 30 days, one for the last 24 hours and one for the last year.

It's much more easier to see how your monitor behaved in the past day, month or year now. Also, for the 30 days view, each column is split in 24 hours so if your website tends to go out at night, you'll see it on the chart.

The availability percentage is now displayed on hover over the (i) next to the downtime in minutes:

The yearly view helps see the long-term availability of a certain monitor, very useful especially to compare or just find out how much downtime did it have in the past year:

Each bar is a month, and for each month you have the daily breakdown, basically you easily get availability information for all the 365 days in the past year.

Admin Updates

• Added heat-map availability charts for monitor, with 24-hours, 30 days and 1 year views (#215)
• Fixed edit monitor loading error on unknown team channel, mainly useful for migrating to the new alerting channels (#217)

API Updates

• Added request to retrieve monitor's chart-friendly availability data (#565)
• Added support for Email outage/recovery alerts via Notifications (#593)
• Added test SMS credits + Tax Rates product creation to Stripe test-data setup command, useful for Continuous Deployment and testing (#610)
• Fixed raw availability request can't handle ISO date strings (#603)
• Fixed use state attribute for hires data (#601)
• Fixed handle subscription() not found case, when we cannot find the corresponding Stripe subscription (#621)
• Fixed end of hour selection for hi-res precision in the availability charts (#614)
• Fixed test error "partial write: points beyond retention policy dropped=1" (#607)
• Fixed call to tax rates creation method (#612)
• Security update of dependencies (#599)

When you've just added a new recipient and you're testing it (via the pencil icon), it's all sunshine and rainbows if you receive the test alert.

But if you don't, and we're getting any error back from the notification gateway driver, you'll see a nice dialog with the actual error message from the driver, quick tips on what to check and a link to the complete guide.

Admin Updates

• Added promo code input option in the Plan screen.
• Added failed recipient test screen with error message, useful tips and links.
• Removed invitation code from the sign up screen and related bonus features.

API Updates

• Added promo code support
• Removed invitation and bonus features.

Mostly a maintenance release but the most notable fact is that the name of a monitor was limited to 30 characters, and now it is increased to 100 characters.

Admin Updates

• Changed monitor name limit from 30 characters to 100 characters #103

Core/API Updates

• Fixed 404 errors in the logs from FirstPromoter when user signed up without affiliate link #591
• Fixed SaaS Metrics test #585
• Fixed missing alert messages in Spanish #588
• Security update of dependencies #582 #592

This update brings plenty of novelty to Monitive, and especially a set of long-awaited features such as:

• Push notification Outage / Recovery alerts via Pushover
• Outage / Recovery alerts via Slack
• Outage / Recovery alerts via Telegram
• A unified place to manage alert recipients called "Recipients"
• Test alert functionality, so you can check if any of the recipients configured are properly set up.

Admin Web App Updates

• Added Recipients management screen, and Pushover integration #161
• Added Ransom IT thank you message in the Monitors list #167
• Added Telegram and Slack alerts #170
• Added onboarding copy variation for free account sign ups #180
• Changed some API attributes to camelCase #166
• Changed Status Page feature copy
• Changed billing page only requires VAT for EU countries #175
• Removed changelog requests and box (not compatibile with the new website) #173)
• Fixed status page monitors list ripple effect
• Fixed Whatsapp support number
• Fixed Recipients screen should only be visible if the user has manageable channels (such as Pushover)
• Fixed chunk load fail errors when the older distribution files weren't available #176
• Fixed monitor group dropdown edit page and add/edit validation feedback #171
• Fixed Slack Webhook URL loading after setting it and before refreshing the page #181

API Updates

• Added Homestead config files for easier development deployment
• Added Test Pushover notification feature, allowing a user to check if Pushover notifications are properly set up #351
• Added trigger so that remove Pushover feature will remove any configured Pushover alerting rules
• Added automatic sync between user's email and phone number to new-style notifications #545
• Added ability to sign up directly to the free Plan #554
• Added saving payments and refunds into a local table (no payment details included) #509
• Added Telegram outage/recovery alerts #559
• Added Slack outage/recovery alerts #552
• Added trigger to removed Status page feature to set pages to Private #576
• Added update of FirstPromoter lead after Stripe customer is created #581
• Fixed removing the phone number would cause an empty hash collision #564
• Fixed duration of the daily retention policy from 85440 hours to 87648 hours (10 years and 2 days).
• Fixed Status page availability chart wasn't including the oldest day, 90 days ago.
• Fixed ThankYouListener to be queued (was sync) #579
• Fixed pausing a monitor created a rogue incident (without end date) #549
• Security update of package dependencies (composer update)

Status pages is a new Monitive feature that will be available to all Monitive Pro users soon. You will be able to create unlimited status pages for any combination of your monitors. We’re still testing it and tweaking it, and making it ready for everyone.

Besides the status page, many fixes and under-the-hood improvements were released.

Fixes & Improvements

• feat: skip latency info & add view page links @dlucian (#163)
• feat: enable users to revoke invitations they’ve sent @dlucian (#159)
• feat: [NEW FEATURE] Manage status pages @dlucian (#156)
• fix: API endpoint URL
• fix: translation string indentation
• fix: storage attribute at signup
• fix: reports pagination @dlucian (#154)
• fix: show second bonus if available @dlucian (#145)
• fix: changelog news drop-in anchor not persisting on Safari @dlucian (#143)
• fix: don’t show NaN when we don’t have latency data @dlucian (#141)
• fix: show reason when cannot disable Team Management @dlucian (#140)
• chore: save signup user source @dlucian (#150)

API Updates

• feat: SaaS Metrics Report @harmandevp (#466)
• feat: send email to team owner when webhook alert fails @harmandevp (#464)
• feat: status page slug format validation message @harmandevp (#510)
• feat: Status Page feature @dlucian (#482)
• feat: flags hasResponseTimes and hasAutomaticIncidents update @harmandevp (#530)
• feat: removes monitor settings from public response @harmandevp (#526)
• feat: encrypts recipient sensitive data @harmandevp (#525)
• feat: saves recipient_id via monitor POST/PATCH @harmandevp (#523)
• feat: manage recipients @harmandevp (#501)
• fix: don’t allow read-only team members to send regular member invitations @harmandevp (#479)
• fix: confirm monitor timeout @dlucian (#488)
• fix: update horizon to use 15 workers instead of 30 as it was causing memory issues #489
• fix: skip throttle for the token generator @dlucian (#493)
• fix: non-owner can only revoke the invitations that he/she sent @harmandevp (#506)
• chore: optimize logging @dlucian (#494)
• chore: update dependencies @harmandevp (#485)
• chore: optimize logging @dlucian (#480)
• chore: send announcement to users @harmandevp (#470)
• chore: add team_id in the weekly report @dlucian (#481)
• chore: send ERROR and above to slack channel #freyja
• chore: save visitor source on signup @harmandevp (#498)
• chore: creates new Ammolite bonus @harmandevp (#515)
• chore: updated dependencies @harmandevp (#497, #511, #508, #500, #522)

We bring two new audit-oriented features today that have been requested and are now fresh out of the oven, ready to use.

Read-only user role

You can now invite read-only users to your team, or you can change the current users to be read-only.

A read-only user cannot start, stop, delete, update or add monitors. It cannot acknowledge monitors, and can only add other read-only members to the team.

However, a read-only user can create and manage custom reports that he creates. Basically it has research rights in your team, but can’t touch anything.

To add users to your team, you’ll have to activate the Team Management feature first.

Name, update and delete custom reports

You can now give a name to each of your custom reports.

You can also update an existing report (causing it to be re-generated) and, of course, you can now delete a previously created report.

To create and manage custom reports, you’ll have to activate the Custom Reports first.

This includes updates on the new SMS credits, notification updates, logging, translations, removing obsolete code and improving our test suite.

Fixes & Improvements

• feat: SMS package acquisition (#123)
• feat: add refresh credits button
• fix: update slack notification username for release
• fix: cannot enable any channel
• fix: cannot load team in the SMS Feature page
• fix: update Blog link
• chore: translations feb 2021 (#121)
• chore: update notify username
• chore: delay loading of GTM

API Updates

• feat: SMS Package acquisition (#418)
• fix: sprinkler connectivity check before run (#463)
• fix: ensure reset password is case-insensitive (#456)
• fix: add only locations that were up to the sitemap (#454)
• fix: refactor altruistic test to not rely on /emails/ (#446)
• fix: trial users don’t get sms_credits (#453)
• fix: free plan maintenance script (#452)
• fix: custom reports - only list current user’s reports (#436)
• fix: cannot rely on /emails/ routes in tests (#455)
• fix: ConfirmMonitor has been attempted too many times or run too long (#460)
• fix: non-ASCII SMS messages taking up 2-3 segments instead of 1 (#459)
• fix MonthlyReportDriverTest.php
• chore: updated dependencies (#465)
• chore: remove Kohana migration code (#461)
• chore: updated dependencies & introducing Logflare (#407)
• chore: add slack notification when deploying master
• chore: chore: notify Logflare on release
• chore: add Slack notification on release
• chore: change initial credit to 200
• chore: batch logflare requests (#450)
• docs: add wopher for homestead docs

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

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)

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)

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.

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)

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)

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

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)

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

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

This update adds the following to 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

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)

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

This allows 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)