Skip to main content

· 2 min read

We push changes to production almost every day and some times multiple times a day. The changes include new product features, bug fixes and any other priority changes required.

Based on customer feedback, we rolled out several changes to monitoring dashboards and also surfaced few metrics around execution time and % success for monitoring checks.

Here is an example screenshot of the new monitor results page:

Monitoring metrics

We clearly show the result trend showing success% for a monitoring check in 24-hour, 3-day and 7-day intervals.

We also show the 90th percentile value for runtime for a monitoring check. The 90th percentile value is widely used to identify performance issue while testing application functionality. We also show a warning if the 90th percentile value for 24-hour window is breaching the 3-day or 7-day interval by over 20%.

There is also a new chart on the page that allows seeing the execution time of the monitor's latest 20 checks for all selected monitoring locations. The chart allows you to visualize the performance based on the location and see a trend for the recently executed checks.

Collection results

Collections allow you to group monitoring checks to test an end-to-end flow or allow grouping multiple monitoring checks to run against multiple environments.

With the recent introduction of Collections, we realized that the experience to view results for a monitor specific to a Collection was complex.

We have simplified this experience with the changes this week. You can now check results of a monitor specific to a Collection.

Here is an example:

Monitoring metrics

The screenshot shows a monitor named User Profile Checker configured to run on Staging and Production using Collections.

The results for this monitor on Staging or Production can now be accessed using the new Collection tiles. Each of the tiles also show the recent results for the monitor in the Collection.

Changes to notifications

The Synthetic Testing and API Monitoring email, Slack, Teams notifications are now updated to reflect the Collection name as well now. This allows you to get more context about a monitor reporting a failure or recovery and prioritize accordingly.

Other updates include:

  • Inconsistent use of shadows vs. borders for tile and card layouts have been fixed. We will consistently use bordered flat layouts.
  • bug fixes

· 2 min read

Today we are announcing the availability of No-Code Editor for defining Synthetic Tests in DevRaven.

Previously, adding a new synthetic test required users to directly define the Javascript code for executing Playwright tests. However we received feedback from our users that directly writing code is hard and some users are not familiar with Javascript and use other languages for automating tests.

Based on this feedback, we added support for No-code Editor which offers ready-to-use actions that can be composed to create an end-to-end flow.

Browser interactions, assertions, miscellaneous actions and custom scripts can be added part of the flows with a simple click. Steps can also be dragged and dropped to change the execution sequence. For complex scenarios, we continue to support the full Scripting Mode.

Editor Actions

We also published content including video for users who prefer to use a browser based recorder to generate the code. Refer Recording Tests for more details on how to use recorder for generating Synthetic tests.

Other updates include:

· One min read

Today we launched support for Multi-Factor Authentication (MFA) for all DevRaven user accounts.

Any user can optionally enable MFA for their user account to prevent unauthoized access to their account due to weak/leaked passwords.

User accounts with MFA enabled are required to enter MFA token during the local authentication (username/password based) login process.

Please note, you will not be prompted to enter MFA token if you use a third-party login provider (such as Google) to access your DevRaven account.

Refer the Multi-Factor Authentication documentation for more details about this feature.

We also pushed few UX improvements to Monitor Scheduling: Schedule changes now require the status to be enabled. This should prevent unintentionally leaving the scheduler in off state when scheduling monitors.

We also published more content about Continuous Web Page Monitoring and Multi-environment monitoring, including video guides!

· 2 min read

I am very excited to announce our newest feature, Collections. Collections allow you to create lists of API tests and browser tests which can be executed in a sequence.

Collections allow you to orchestrate tests against your web apps or APIs and make it possible to monitor complex user scenarios. Add tests to a Collection, drag-and-drop to change the order and perform operations as invoked by your real end-users.

Here are a few possibilities:

Workflow Monitoring

Monitor your workflows my composing API tests and Playwright based browser tests with optional delay between each step. Example scenarios such as:

  • Monitor your long-running workflows - ensure your end-to-end flows are working as expected and no regressions are introduced with newer changes
  • Monitor your ML training jobs - ensure your training servers are up and running
  • Monitor integrations - perform operations on your source service and assert the expected output on the target service.

The video walks you through a quick example for setting up workflow monitoring.

Monitor multiple environments

Create monitors or tests for your application functionality and continuously run them against your dev, staging, pre-prod and prod environments. By associationg Collections with specific Environments, the same tests can run on all your environments and any regressions in existing features can be identified.

Refer Multi-environment monitoring for more details.

We will a producing more content and videos discussing varieties of use cases in the coming days. Subscribe to our YouTube channel to receive our updates.

· One min read

I am happy to announce the support for Opsgenie integration. All DevRaven Workspace (including free plan Workspaces) can use the integration without additional charges.

The integration also supports dispatch of events from one monitor to multiple Opsgenie Teams. Documentation with step-by-step instructions for enabling the integration is available here

Few other updates that were rolled out include:

  • An example recipe for using Jest's expect for assertions
  • Monitoring results page now show the time taken for execution. Please note that if you have multiple monitoring locations enabled for a monitor, this value can be for any monitoring location.
  • few minor bug fixes

· One min read

Reusable functions is one of the most asked feature by our early access customers. Reusable functions help prevent duplication of code across multiple monitoring checks.

Functions defined in a Workspace can be invoked from Scripts in Synthetic Tests or API monitoring checks. For more details about Functions, refer the documentation here.

PagerDuty integration is now available. More details on PagerDuty website and also refer our documentation here

New availability of persistence APIs to write/retrieve values to temporary storage for monitoring complex dependent scenarios. Refer documentation here

As we get closer to public availability of the product, we also integrated with Stripe for subscription management and billing. We also clarified our Pricing details on our public website.

Few other updates include:

· One min read

We are excited to announce availability of API monitoring for all customers in all the available monitoring regions.

API monitoring allows you to setup and monitor your critical REST end points to ensure they are working as expected. Similar to other types of monitors, you can also setup monitoring schedules to run your test at regular intervals. Currently the lowest interval we support for executing tests in all regions is 5 minutes.

We also updated the documentation to clarify the data retention periods for monitoring data. All preview and free plan workspaces will have a data retention period of 10 days and paid workspaces will have a default data retention period of 30 days.

Few other updates include:

  • Manage Workspace (rename or delete Workspace)
  • The ability to snooze or view snooze status from list view for all monitors.
  • Support for adding tags to monitors
  • other bug fixes

· One min read

Starting June 6th, 2022, DevRaven will be available as limited preview release. This release will help us gather feedback for fellow developers on the features and course correct the roadmap based on customer needs.

The features available include:

  • Synthetic Monitoring
  • SSL Monitoring
  • Web Page Monitoring
  • User Management including invite user flows.
  • Roles
  • Workspace Management
  • Global alert settings

More features are in the works and changes get deployed everyday.

We hope you find DevRaven useful for your development and operations needs. If you have any questions or feedback or need a 1-1 session to help you get started, please reach out to [email protected]