a9s LogMe for PCF¶
This documentation describes the a9s LogMe. a9s LogMe enables on-demand provisioning of VM-based, dedicated LogMe (ELK Stack) servers and clusters. Developers can create instances of a LogMe server or cluster using Apps Manager or the Cloud Foundry Command Line interface (cf CLI), and bind these instances to an application to monitor it, or use them to monitor services. Depending on your service plan, a service instance may be associated with a single, dedicated VM, or a set of VMs consisting of multiple VMs containing a LogMe cluster.
a9s LogMe enables on-demand provisioning of VM-based, dedicated LogMe servers. App developers can create instances of a LogMe server using Apps Manager or the Cloud Foundry Command Line Interface tool (cf CLI) and bind these instances to an app to monitor it or use them to monitor services. The service runs on a single, dedicated VM, the size of which depends on your service plan.
a9s LogMe automatically provisions service instances and creates a dedicated VM for each instance. This isolates service instances, preventing the "noisy neighbor" problem that can occur when multiple service instances run on a shared VM.
Because the service provisions VMs as needed, only existing service instances use infrastructure resources. These resources are released when service instances are destroyed. With on-demand provisioning, the number of service instances grows or shrinks based on demand.
a9s LogMe includes the following key features:
|On-demand service instance provisioning||a9s LogMe deploys LogMe instances automatically. Developers can provision a LogMe service, on a single-VM or cluster of VMs, using the single command |
|Service instance isolation||Each LogMe server runs on a dedicated VM to ensure noisy-neighbor protection and align with enterprise security requirements. |
a9s LogMe uses Cloud Foundry application security groups (ASGs) to prevent network connections from unauthorized apps.
|Smoke tests||A post-deployment, smoke-test errand runs basic tests against your installation, ensuring that it is configured properly.|
|Deployment updater||An updater errand updates the stemcell and all provisioned a9s LogMe for PCF service instances to their latest version.|
Specification of a9s LogMe service plans:
|High Availability |
(number of nodes)
|Number of vCPUs||2||2||2||2||2||2|
|RAM||2 GB||2 GB||4 GB||2 GB||4 GB||4 GB|
|Disk *||4 GB||10 GB||50 GB||10 GB||50 GB||150 GB|
For example, one backing service instance of size m is high available (consists of 3 nodes), has 2 vCPUs, 4 GB RAM, 50 GB disk and logging component.
* Total virtual disk size. You cannot use the whole disk for your data. For more information, refer Disk Alerts.
Any questions left?
Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.