Metrics & Logs version 7.7 released

Today we’re excited to announce the Metrics and Logs 7.7 release that adds Microsoft Azure performance monitoring for virtual instances, databases, and other resources!

You can now monitor all of your virtual machines (instances) and SQL instances running on Microsoft Azure and filter by the tenant, management group, or subscription.
That allows for short-term but also long-term performance monitoring as Metrics & Logs stores the data over months and years (based on your configuration).

As always there are many other improvements that come with version 7.7.

Improved Auditable Change Management

Our highly popular feature connects to your VMware management (one or many vCSA) and collects the most important ESXi hardware, VM hardware and configuration changes as well as the virtual machine location over time. Additionally, we can even detect when certain operating systems are installed (and running) or applications like Oracle database, Microsoft SQL Server, or Oracle Java are running.

Features and reporting performance have greatly improved to support thousands of entities.

The screenshot shows the changes that happen to your virtual machines over time. Of course, you can create reports based on that and query in real time.
Auditable Change Management

This information is not simply stored in a common database, it’s immutably stored using the immudb database. That provides the foundation for a change audit, as you have cryptographically-verifiable proof of any change that happened.

Our customers are already using this auditing capability to prove to vendors such as Oracle or Red Hat which systems and applications are running where and when. To do so, the VM location (ESXi, cluster, network) and VM resource changes (CPU, memory, network) need to be tracked complete and tamper-proof.

Improved Automatic Workload Detection

Another very useful feature is the automatic detection of operating systems and applications where resource usage and location are relevant for the resulting license costs.
Detect VM workloads

Today the automatic detection supports:

  • Red Hat OS
  • Microsoft SQL
  • Oracle Database
  • Java runtime

Please contact us if you miss an important vendor on our list for your license tracking.

WHERE TO GET THE NEW VERSION?

Existing customers can find the latest patch in our customer portal and everyone who likes to evaluate Metrics & Logs can simply start a trial:

NEW FEATURES AND EXTENSIONS

  • Microsoft Azure metrics and data collection incl. new dashboards
  • improved Auditable Change Management: Crawler, Dashboards, Reports
  • increased compatibility with legacy VMware versions
  • better handling when vCenter fails
  • Cisco Hyperflex update for newer versions
  • reduce database load caused by syslog feeder
  • Vscsistats Dashboard: display improvements
  • improved CPU Ready calculation
  • optimize speed and disk usage for tamperproof log storage
  • more NUMA metrics
  • collect uptime metrics for VMs and Hosts, new dashboard for uptimes “VMware Health: System Uptime
  • Esxtop-based device queue metrics
  • more HBA adapter queue metrics
  • more multipathing metrics
  • support influx FLUX QL
  • improved UCS Crawler performance

Of course, we fixed and updated all of our software components.

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.