After successful migration of our monitoring front-end, back-end and microservices to .NET Core 2.0 and .NET Standard 2.0, here is quick summary of this process. Migration decision Although we were very very satisfied with .NET Core 1.0, we decided for migration to newest version for following reasons: bigger API and more libraries available (thanks to .NET Standard 2.0) much easier to share common internal projects between .NET Core 2.0 and Full .

We are currently implementing experimental subset of WebDriverIO API (higher level API on top of Selenium WebDriver) in .NET Core so we could run synthetic (transaction) monitoring very efficiently from different geographic locations. Implementation goals: cross-platform, efficient and lightweight framework easy to use (REST API / web interface) high compatiblity with WebDriverIO because users are already familiar with it for security reasons we will probably implement simple JavaScript interpreter for WebDriverIO commands (instead of running tests in Node.

Dear developers, Today we published REST API documentation which allows you to write your own clients to access most frequently used AppBeat functionality. If you have any questions, please let us know, we’re always here to help! And as always - happy monitoring!

We would like to share with you very interesting NDC Conference session from Sydney which describes pros and cons of a microservices solution and how you can build one using .NET and a number of open source tools like EventStore, RabbitMq and Redis. Presentation was done by Richard Banks and you can watch it on YouTube:

That is our goal for next year! We want to offer you real browsers, for example Chrome and Firefox, so you can periodically check if your web application always behaves as it should. This kind of service will be very useful for your continuous integration and testing your website after you deploy new version into production environment. If you would like to participate in closed beta, please contact us.