In newest AppBeat version 1.7.0 you can now define quiet hours for your users, services and/or third-party integrations (I will refer to these as "resources").
Quiet hours are recurring time periods during which alerts (outgoing notifications) are muted for selected resource(s). Quiet hours does not affect monitoring, just notifications. This means that you will always be able to check log entries, even during effective quiet hours.
You can access this new feature from "Alerting" module and by clicking "Quiet hours" tab as shown below:
When you click "Add quiet hours for" button for specific resource, you will be presented with dialog similar to this:
You can add multiple quiet hours for same resource, AppBeat engine will always aggregate those entries while determining if quiet hour is effective or not.
Here are some use case examples:
- you have service which is not operational 24/7 - now you can simply set quiet hours when service is not active so you don't receive any alerts
- you have recurring (nightly) updates and you want to mute alerts during this period
- you don't want to receive alerts for less important service(s) during weekend
- your team member goes on vacation or sick leave and you don't want to bother him/her with outage alerts
- some of your team members receive alerts only during working hours (and you have dedicated team for 24/7 operations)
We published new web application with improved UX and some new useful features:
- you can now quickly filter your checks on "Live status" screen:
- added quick actions for monitored checks and services
- "Live status" simplifications due to new quick actions feature
- Check wizard should now have better support for high DPI displays and show vertical scrollbar where needed
- Added option to easily clone monitored check (this allows you to quickly create similar monitors)
- "Live status" - dismiss all alerts is displayed when there is more than one service alert. Previously you had to click "dismiss alert" for each monitored service.
- new API methods: added dismiss-service-alert and dismiss-all-service-alerts endpoints
- other minor improvements & optimizations
If you find any issue please let us know.
AppBeat website monitoring allowed you to easily create public status page for a long time. This page is hosted on our domain by using URL in following format: https://appbeat.io/status/YOUR_STATUS_PAGE_ID
However some users wanted more:
- hosting public status page on their own domain
- use their own CSS styling
We are happy to announce that newest AppBeat allows you all that!
If you navigate to "AppBeat / Public status / Dashboard" you will be able to enable your status page from there and publish on your web server static HTML file, similar to this:
<!--Please copy css style to your web server because we could rename it in future-->
<link rel="stylesheet" type="text/css" href="https://appbeat.io/assets/css/status-page.css" />
<!--AppBeat status page is rendered into element with id appbeat-status-container-->
<div id="appbeat-status-container" class="status-layout"></div>
<!--Load AppBeat status page script for your page and start rendering it-->
<!--Tip: your script is also duplicated on https://web2.appbeat.io which is hosted in different region-->
Every time your visitor navigates to this page it will show him/her latest status of your page.
Method 2: creating public status page on your domain by getting embeddable HTML fragment on your server side
Both methods can be styled with your own CSS or you can use our default style located at: https://appbeat.io/assets/css/status-page.css
Good thing about this solution is also, that you don't have to change DNS settings to get it to work. Simply publish static HTML file on your web server or embed our HTML fragment if you use dynamic pages. And that is it!
If you would like to try this feature, you can register for new free account and please contact us so we can enable your 14-day risk free trial.
Please note, that for limited time we offer you 60% discount on Starter plan.
Today we published new web application with one of the most requested feature for our advanced users - multi-user login!
This functionality is very suitable for larger companies and DevOps teams, where it is prefered for each member to have its own AppBeat sub account (and not sharing primary account with all your users anymore).
Currently it is possible to add up to 25 power users for your subscription. These users have very similar permissions to primary account administrator with following restrictions:
- they can not deactivate primary account
- they can not change account personalization
- they don't see account log
Based on your subscription plan you can have:
- Standard plan - 3 Power Users
- Advanced plan - 10 Power Users
- Enterprise plan - 25 Power Users
If you need more than that, please contact us and we will arrange you more users. In future versions we plan to add more roles with less permissions (for example only to view data without any changes).
Hopefully you will like this new feature! And as always - happy monitoring!
Yesterday we published AppBeat 1.4.6 which now natively supports Pushover and StatusPage.
With Pushover you can now easily receive outage notifications on your Android or iOS phones, and with StatusPage you can automatically publish detected outages on your public status page.
With this version we also add support for message personalization for most third-party integrations:
All third-party integrations can be managed in "Account / Integrations" section:
On September 8th we deployed AppBeat 1.4.3 which brings you more detailed logging for your web monitors. If error occurs we will save server response (HTTP body with header) and send you unique link where you or your support team can view it. Previously you would receive just HTTP status code.
Detailed logs can now help you to diagnose root cause of problem more quickly. They also allow you to keep historic track of incidents (please see note below about how long we keep your detailed logs).
List of all changes are:
- improved logging for all web checks created after August 9, 2016 - when check changes state from good to non-good we now save detailed error message with response body and header (if available). Older web checks will be migrated to new model gradually.
Note: we will keep your detailed server response for limited time, based on your subscription level:
- Free: 1 day
- Basic: 7 days
- Starter: 1 month
- Standard: 3 months
- Advanced: 6 months
- Enterprise: 1 year
- adding or editing checks: you can now select service by entering service name (especially useful if you have large number of services)
- downtime calculation returned error if user previously edited check and changed service
- other minor improvements
We are continuing with our rapid development and last week new version was published (1.4.2).
In this version we introduced new powerful report - Logs & Performance, and published final version of downtime report. Here are some screenshots of new features.
Performance statistics & hourly averaged response time chart for your periodic check:
Filtering monitoring logs:
As you may noticed, we now also allow you to filter logs and calculate downtime reports by "service group". Service groups are optional groups useful especially for larger organizations. It allows you to group any combination of your services into its own group. Those groups can then be used to assign email/SMS contacts for error notifications (contacts can be members of service groups), or they can be used for filtering data in reports.
List of all changes in version 1.4.2:
- improved "Downtime overview" report (added downtime tooltips to timeline, added aggregated check report in service details). It is now out of beta.
- new added "Reports / Logs & Performance" module for more powerful log analysis (you can drill down your data to lowest check level)
- removed removed "Reports / Statistics & Logs" (replaced by new, more powerful reports)
- update simplified "Live status" tiles & optimizations
- update other minor improvements
We are already working on some new useful features for next version! Stay tuned...
Yesterday we published new AppBeat version with improved downtime report. We also added service timeline where you can visually track details about downtimes:
List of all changes for version 1.4.1:
- improved "Downtime overview" report (added more filters and options, added uptime/downtime timeline, more accurate service downtime calculation - if multiple checks on same service fail at same time, we now automatically exclude overlapping intervals)
- update "Service groups" tab moved to "Services & Checks"
- removed removed "Uptime" component from "Statistics & Logs" (replaced by more powerful "Downtime overview" report)
bug fix context menu could not be entirely visible if item was clicked in bottom or right part of browser window
- bug fix some dialogs did not display vertical scrollbar if there were too many items
- update other minor improvements
In next version we plan to release final version of downtime report and then we will continue with new "Log and Performance" report, which will be much more improved version of current log report.
Yesterday we rolled out new version of AppBeat which brings fully customizable website monitoring (as promised in previous post):
List of all changes:
- more friendly wizard for creating new checks
- update web monitor is now fully customizable (you can post data, change protocol version, IP version, send custom headers, ...)
- update DNS monitor can now accept IPv4 or IPv6 address of DNS server used for querying
- removed "Automated Web Testing" early preview is now removed from UI because we received enough initial feedback. Thanks to all who participated in this preview!
- update other minor improvements
If you find any issues or have questions, please let us know!
In new version of AppBeat (1.3.8) we added new option under "Reports / SQL Archive Analyzer". You can now create your own SQL filters to get archived log data that you need (basic SQL knowledge required). Data can also be exported to CSV files.