opvizor-performance-analyzer-vmware-horizon-view-performance

Since we started the Performance Analyzer development some years ago, it was always important that our customers cannot just monitor and analyze the VMware vSphere performance, but also checking the applications and the underlying hardware.

The integration of VMware Horizon View Performance is another step into that direction to monitor the virtual desktop performance from inside the guest and not just the outside view using VMware vCenter data.

That offers a single view that provides visibility from the end user VDI experience to operating system, storage and network issues. All critical metrics are tracked for PCoIP and VMware Blast, gathering data for logon duration, frames per second, data transfer and application, OS and ESXi performance.

Our latest version 4.9 is ready to integrate data from all of your virtual desktops to get performance data from PCoIP and the new VMware Blast protocol.

The architecture consists of a Guest agent that runs within your Microsoft Windows virtual desktops as a Windows service and gathers all required PCoIP or Blast metrics, depending on the protocol you´re using and the VMware View dashboard that makes sense of the received data in a simple and efficient way.

The dashboard merges information of the Guest OS, VMware VMkernel information and PCoIP or Blast metrics.

VMware Horizon View Performance PCoIP

Especially critical metrics like Frames per Second, RTL or Packet loss are directly visible. Furthermore you can check if network bandwidth is taken using USB devices.

VMware Horizon Blast Protocol

Combined with VMware Performance data directly from the VMkernel it makes a complete picture!

VMware View Blast combined with VMkernel Performance

These are the metrics we´re collecting:

PCoIP Session Metrics

  • Session Duration Seconds
  • Bytes Received
  • Bytes Sent
  • Packets Received
  • Packets Sent
  • RX Packets Lost
  • TX Packets Lost

PCoIP Session Network Statistics

  • Round Trip Latency ms
  • RX BW kbit/sec
  • RX BW Peak kbit/sec
  • RX Packet Loss %
  • TX BW kbit/sec
  • TX BW Active Limit kbit/sec
  • TX BW Limit kbit/sec
  • TX Packet Loss %

PCoIP Session Imaging Statistics

  • Imaging Bytes Received
  • Imaging Bytes Sent
  • Imaging RX BW kbit/sec
  • Imaging TX BW kbit/sec
  • Imaging Encoded Frames/sec
  • Imaging Active Minimum Quality
  • Imaging Decoder Capability kbit/sec
  • Imaging Megapixel/sec

VMware Blast HTML5 MMR counters

  • Received Packets
  • Transmitted Packets
  • Received Bytes
  • Transmitted Bytes

VMware Blast Imaging Counters

  • Dirty frames per second
  • Poll Rate
  • FBC Rate
  • Frames per second
  • Received Packets
  • Transmitted Packets
  • Received Bytes
  • Transmitted Bytes

VMware Blast Session Counters

  • Received Packets
  • Transmitted Packets
  • Received Bytes
  • Transmitted Bytes
  • Jitter (Uplink)
  • RTT
  • Packet Loss (Uplink)
  • Estimated Bandwidth (Uplink)

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.