how-we-use-new-relics-docker-integration-at-opvizor

How we use New Relic and Docker at Opvizor

New Relic, Inc, the software analytics company, announced recently an addition of features for Docker container monitoring, currently in open public beta. 

Docker is now widely used, or at least evaluated, in enterprise environments for its strong modularization and application distribution capabilities. Docker containers can be described as runtime environments with many of the core components of a virtual machine and isolated services of an operating system, especially designed to make packaging easy and execution of services smooth. 

Docker Container Technology

Container technology such as Docker provides an ideal environment for deployment of services with regards to speed, isolation management, and lifecycle.

Docker at Opvizor

Docker’s popularity has soared since it was introduced and, up until now, it has been an issue to get quality insights into the containers resource usage and its impact on application performance.

New Relic analysis capabilities promise to solve this problem, by connecting to Docker containers and providing the same feedback as it currently does for the other types of hosts. The technology includes:

  • Possibility to compare application performance before and after deployments
  • Monitor transactions in order to pinpoint the cause of performance bottlenecks
  • Transactions are traced across tiers and services of an app to provide end-to-end visibility

Having the possibility to track these metrics within Docker containers will be another step towards widespread adoption of Docker and adaption to its features. For more information on how to enable New Relic for Docker containers, check https://docs.newrelic.com/docs/servers/new-relic-servers-linux/getting-started/new-relic-servers-docker

Opvizor on-premise

Here at opvizor, we use Docker on our on-premise version, taking advantage of containers to provide the best multi-functional application on a single virtual machine that our customers can deploy in their datacenter. When making the decision to choose Docker, even at the very early stages of its development, we took into account how its potential could help us implement a robust, secure, easy-to-deploy application. Our expectations have been met and we have been improving it as Docker itself has been steadily releasing new features.

Opvizor and New Relic

We also currently use New Relic to monitor our cloud platform in terms of resources and bottleneck identification. It has proven very important for our record of minimal downtime since its adoption.

New Relic at Opvizor

With new relic’s announcement of docker support, our developers can now also have an overview on containers data. This will help opvizor’s team to optimize resources and transactions also on the on-premise edition, enhancing its performance to ensure the most efficient use of customer’s datacenter resources.

Opvizor offering

Opvizor aims to deliver both on-premise and cloud solutions to its customers, encompassing the whole spectrum of users. The ones with constraints regarding using an application outside their datacenter have the possibility to choose our on-premise version, dockerized, and soon monitored by New Relic. For users which the main concern is to save resources on their own datacenter, we offer a cloud version already monitored by New Relic.

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.