Step-by-Step Instructions on Getting Started with Bitbar Monitoring
Proactively monitor user experience and performance of your mobile app, web and back-end API.
Step 1: Create a New Account or Sign In with Your Bitbar Testing Account
Note: If you already have a Bitbar Testing (Testdroid Cloud) account, you can already sign into Bitbar Monitoring now.
To get started, create a Bitbar account. By hitting the button below, you will be taken to Bitbar Testing signup page for account creation. Once you activate your account, you are good to go. Create once, use it for both Bitbar Testing and Bitbar Monitoring.
Step 2: Create and Select the Type of Monitoring Check to Run
HTTP GET. The HTTP GET is a basic API check to verify that some endpoint is responding and returns an expected return value. With the HTTP GET, it is possible to add a regular expression check for additional validation of the received response message.
Page Load. The user-provided web address is opened using a Safari (iOS) or Chrome (Android) web browser. Until the page is loaded, all network communication is tracked and reported into the check run. With a Page Load functionality, it is possible to create an additional regular expression check on the main source file downloaded. If additional content checks are required then the use of Appium check is highly recommended.
Appium Test Automation. Functional and web content checks can be created using Java and Appium. An Appium check can be developed remotely on developer’s machine and then uploaded with the application under test to Bitbar Monitoring for monitoring checks. Appium supports testing of native, hybrid and web applications on iOS and Android platforms and provides a versatile use cases for various types of mobile monitoring checks.
If you need help to get synthetic monitoring up and running, we are here to help.
Step 3: Select the Right Parameters, Location and Preferences
Physical, Real Location for A Monitoring Check. The first thing is to select on which physical locations you want your monitoring check to happen. This also includes a variety of different real networks in the same cities/countries.
Frequency for a Monitoring Check. Next is to define the interval for your monitoring check. We've provided the most widely used frequencies (15min, 30min, hour, 2 hours, 3 hours, 4 hours, 6 hours, 8 hours and daily) as default. In addition, we also provide the customization of frequency to tailor your unique need.
Actions for An Alarm After Incidents. Bitbar Monitoring provides very flexible and versatile options to alarm the right people or instance when errors, failures or something unexpected things happen with your mobile products. For example, you can define email, Slack, PagerDuty or simply wait (and check again later) when something unexpected things happen.
- EMAIL: Sending an email is useful for reporting of a happened event but typically is not reacted to very fast. Mailing groups are great to get a wider recipient audience for the failing check.
- WAIT: Sometimes it is alright for a check to fail once, or twice, before it is necessary to start further investigation. The wait time is of the same duration as the check interval. A wait means that it is not necessary to jump on the current failure, but let’s wait for the following checks results.
- SLACK: Failures that require immediate attention are good to be sent as messages to a shared Slack channel.
- PAGERDUTY: PagerDuty is an information gathering platform where various systems may send their notifications. PagerDuty provides means to handle the incoming events and take appropriate actions on them.
Step 4: Review the Results of Monitoring Checks
Bitbar Monitoring provides results quickly, with rich details. When you’ve started a monitoring check for any of mentioned products, you can review results under your check dashboard, for example:
Click any of your monitoring check and you’ll get rich details of what is going on, how is the performance of your product (app, game or website) and what has been the general availability of the service. All this data is presented as graphical and textual details.
To inspect a specific monitoring check, simply click filter on the bottom (OK, Timeout, Fail, Error, Skip) and you’ll get the full view of all your monitoring checks at Bitbar Monitoring.
If you would like to know more details on Bitbar Monitoring, you can schedule a personalized online demo with us.