Architecture
Diese Seite ist noch nicht in deiner Sprache verfügbar. Englische Seite aufrufen
Logme is built on a managed stack of OpenSearch, Fluentd, and OpenSearch Dashboards, providing a complete logging and monitoring solution.
Core Components
Section titled “Core Components”OpenSearch
Section titled “OpenSearch”OpenSearch serves as the central search and analytics engine, storing and indexing your application and service logs. It enables fast searching and querying across large volumes of log data.
Fluentd
Section titled “Fluentd”Fluentd acts as the log collection and forwarding layer, gathering logs from various sources and streaming them to OpenSearch for storage and analysis.
OpenSearch Dashboards
Section titled “OpenSearch Dashboards”OpenSearch Dashboards provides the visualization interface, allowing you to create dashboards, explore logs, and analyze data through an intuitive web UI.
Infrastructure architecture
Section titled “Infrastructure architecture”Service instance isolation
Section titled “Service instance isolation”Each Logme service instance runs on dedicated virtual machines in the STACKIT Compute Engine. This ensures isolation from other services and protects against resource contention (bad neighborhood protection).
Deployment separation
Section titled “Deployment separation”Logme services created through Cloud Foundry and those created via STACKIT Portal/CLI are completely separated. Services created in one environment must be managed and deleted in the same environment - cross-environment management is not supported for technical reasons.
Single Node vs. Cluster
Section titled “Single Node vs. Cluster”Single Node
- Runs on a single VM
- Suitable for development and testing
- Not recommended for production use
Cluster (Replica Set)
- Consists of 3 nodes distributed across multiple availability zones
- Provides high availability and fault tolerance
- Recommended for production workloads
- Ensures service continuity even if a node or availability zone fails
Network access
Section titled “Network access”Logme instances are accessible via public IP addresses, allowing integration with:
- Cloud Foundry applications
- Kubernetes workloads
- Virtual machines
- External systems
Access is secured through ACLs (Access Control Lists) and instance-level authentication.
Data management
Section titled “Data management”Backup system
Section titled “Backup system”The integrated Backup Manager automatically creates full backups every 4 hours and retains them for 14 days. You can also trigger manual backups and restore from existing backups through the service dashboard.
Scalability
Section titled “Scalability”Logme uses a t-shirt sizing model with predefined service plans. When your workload grows, you can upgrade to a larger plan with more resources (vCPU, RAM, disk space).