Beeks Analytics unlocks extraordinary insights into network performance and gives our clients the ability to measure and monitor key metrics with unprecedented speed, accuracy, and flexibility.

Beeks Analytics solves use cases like:

  • Do I have performance problems with any of my trading counterparties?

  • Is the problem inside my infrastructure or outside my infrastructure?

  • I need an overview of the flows going across my network to assist with troubleshooting and capacity.

  • I need to report on performance of my trading system to my customers.

  • I need to exactly reproduce a period of sub-par performance in my trading system to try some possible solutions.

Beeks Analytics is available in two configurations:

  • Beeks Analytics for Markets (BAM)
    BAM is our out-of-the-box configuration, which monitors communication at the edge of your network and/or specifically the performance of other trading venues that you connect to.

  • Beeks Analytics Enterprise (BAE)
    BAE is a bespoke deployment that is fully customisable. BAE can measure latencies anywhere in your network.

In this document, we provide information based on the BAM templated deployment. These metrics will also help our BAE clients plan their custom latency analytics for complex workflows.

For more information about the Beeks Analytics for Markets templated deployment, see the Beeks Analytics Data Guide.

Beeks Analytics architecture benefits

The goals behind the Beeks Analytics architecture are threefold:

  • To operate with an open architecture, which provides the benefit of multiple high volume integration points with your organisation’s own systems.

    • This allows your organisation to fully own the data produced by the Analytics system.

    • It also allows your organisation to run the Analytics software on their own hardware if this is more efficient for them.

  • To allow open scaling, which allows the capacity of the system to handle load to scale up with commercially available server hardware improvements.

  • To be modular and licenced to support open consumption.

    • This means that, for example, if you only need the high performing VMX-Capture layer and don’t require the in-depth analytics that the VMX-Analysis layer provides, we’ll make sure the software is licensed and priced accordingly.

    • It also means that we’re transparent about the drivers of our pricing - core count required for the analysis, which we make clear in our transparent performance metrics.

For more information about the Beeks Analytics architecture as a whole, see the Analytics Concepts Guide.

This document supports the open architecture goal because it shows you how you can take advantage of the high volume performance of Beeks Analytics to take control of your performance data, of your wire data, and of application data that is derived from the wire.

The Beeks Analytics open scaling has the following benefits:

  • It allows clients to take advantage of the performance gains of Beeks Analytics to provide analytics on more data than they were previously able to

  • It allows clients to consolidate their existing monitoring, reducing their operational costs

  • It allows clients to have more long-term predictability of their monitoring costs by using their own hardware to provide their wire monitoring.

  • This document can be read in conjunction with the Beeks Analytics Appliance Hardware Options Guide to guide users on the appropriate Beeks Analytics appliance to support their deployment, or to understand what hardware they should procure to support the Beeks Analytics software.

This document supports the open consumption goal by providing transparency about the performance characteristics of our software, including capture rate, load, and analysis rate.

This document focuses in particular on the performance characteristics of the VMX-Capture part of the Beeks Analytics architecture. This is the part of the Beeks Analytics architecture which handles the highest load. Beeks Analytics Enterprise users may find themselves wanting to configure elements of VMX-Capture or VMX-Analysis beyond the standard template - this document is intended to help them understand how these configuration changes affect system performance, and which elements of the configuration can be tuned to achieve optimal performance.

For more details on how to configure VMX-Capture, see the Configuration Guide for VMX-Capture.

For more details of how to configure VMX-Analysis, see the Beeks Analytics Configuration Guide.