cnil-metrics-logs-7-5-released

After a long period of adding new features, bug fixing and testing we’re excited to announce the Metrics and Logs 7.5 release.
Before we get into bug fixes and improvements, we are thrilled to highlight an absolute innovation that brings significant savings in licensing costs. If you can reduce the number of CPU cores to license because you can now prove that nothing has moved or changed, you can potentially save tens of thousands, hundreds of thousands or more dollars/euros.

Auditable Change Management

Our new software functionality 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.

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 realtime.
Auditable Change Management

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

Our customers are already using this audit 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.

Virtual machine location tracking

We decided to use a swimlane diagram that allows you to track your automatic (DRS) or manual VM migration.
VM location changes

If you feel more comfortable using table views, we provide a new dashboard to get a quick overview of all migrations that happen within or across VMware vSphere clusters.
VM cluster movement

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 in 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 click Start trial on our website.

new Features and Extensions

  • configure Log compliance retentions
  • Auditable Change Management: Crawler, Dashboards, Reports
  • Added NUMA Recommendation engine
  • collect Numa Configuration Metrics from Hosts and VMs
  • added ESXi power management metrics
  • Added HW Version to Metrics
  • Diagrams for Appliance metrics
  • Limit to TLS v1.2, only high and medium ciphers
  • Reports based on immudb
  • index compaction for immudb
  • Enable large_dir mode for filesystem

Of course we fixed and updated all of our components that includes improved image rendering (for alerting), updated vCenter diagrams and many dashboard updates.

CNIL Metrics & Logs

Self-Hosted performance monitoring and compliant log analysis for VMware vSphere, container and much more.

immudb

Built on the fastest immutable ledger technology. Open Source and easy to use and integrate into existing application.

Codenotary Cloud

Trusted CI/CD, SBOM and artifact
protection with cryptographic proof.
One CLI to manage all.

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.