Introduction to TIBCO LogLogic® Enterprise Virtual Appliance
This guide helps administrators to deploy TIBCO LogLogic® Enterprise Virtual Appliance (LogLogic EVA) or TIBCO LogLogic® Enterprise Virtual Appliance - Container Edition (LogLogic EVA - Container Edition) on virtual, container, and cloud platforms.
LogLogic® EVA and
LogLogic® EVA - Container Edition are virtual versions of the
TIBCO LogLogic® Log Management Intelligence hardware appliance, and are distributed on the
TIBCO eDelivery website.
Characteristics and Limitations
The following table summarizes the characteristics and limitations of LogLogic EVA and LogLogic® EVA - Container Edition on different platforms.
| Feature | VMware | KVM | Docker (Container Edition) | AWS | Microsoft Azure |
|---|---|---|---|---|---|
| Installing
LogLogic LSP
For installation instructions, see TIBCO LogLogic® Log Source Packages Installation and Upgrade Guide. |
Yes | Yes | Yes | Yes | Yes |
| Maximum number of devices (includes device groups as well as individual log sources) that can connect to LogLogic EVA | 100,000 | 16,000 | 16,000 | 16,000 | 16,000 |
| Raw data retention | 10 years | 10 years | 10 years | 10 years | 10 years |
Maximum local storage
|
32 TB on EXT4 file systems | 500 GB on EXT4 file systems (addition of local storage is not supported) | Addition of local storage is not applicable, as local data is stored in the
/loglogicdirectory on the volume associated with /loglogicthrough the storage driver of the container service. |
32 TB on EXT4 file systems | 32 TB on EXT4 file systems |
| Expanding the external storage
To purchase additional licenses and for steps on how to expand the storage, contact TIBCO Support. |
By attaching additional virtual SCSI hard drives to the instance | Yes | N/A | By attaching additional virtual SCSI hard drives to the instance | By attaching additional data disk drives to the instance |
| Dynamic memory configurations | In LogLogic EVA, memory for all Advanced Feature engines (MySQL, Indexer, and Tomcat) is dynamically allocated. Configurations are applied based on the memory configuration of the virtual hardware. For details, see Dynamic Memory Configurations. | ||||
| Cloning a LogLogic EVA instance | No | No | N/A | No | No |
| Archiving | Yes | Yes, using NFS | Yes | Yes | Yes, using NFS |
| Backup and restore | Yes | Yes, using SCP | No | Yes | Yes |
| High availability | Yes | Yes | No | No | No |
| IPv6 addresses | Yes | No | No | No | No |
| Configuring as a Management Station | Yes | Yes | Yes | Yes | Yes |
| Upgrading via TIBCO LogLogic® Management Center | Yes | No | No | Yes | No |
| Integration with TIBCO LogLogic® Compliance Manager | Yes | No | No | Yes | No |
| Check Point Log Exporter API (LEA) | Yes | No | No | Yes | Yes |
Related Topics
- Minimum Hardware Requirements
- Installation and deployment instructions:
- Additional Configurations for LogLogic EVA
- Upgrading instructions: See Configuration and Upgrade.
Copyright © 2020. Cloud Software Group, Inc. All Rights Reserved.
