a9s LogMe for PCF (Beta)
IMPORTANT: The a9s LogMe for Pivotal Cloud Foundry (PCF) tile is currently in beta and is intended for evaluation and test purposes only. Do not use this product in a PCF production environment.
This documentation describes the a9s LogMe for PCF tile. a9s LogMe for PCF enables on-demand provisioning of a pre-configured ELK (Elasticsearch Logstash Kibana) Stack. The ELK stack makes service and application logs queryable, visualisable and scalable. 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 for PCF 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 for PCF 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 for PCF includes the following key features:
|On-demand service instance provisioning||a9s LogMe for PCF 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 for PCF 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.|
The following table provides version and version-support information about a9s LogMe for PCF:
|Release date||August 24, 2017|
|Software component version||v0.9.0|
|Compatible Ops Manager version(s)||v1.8.x, v1.9.x, v1.10.x, and v1.11.x|
|Compatible Elastic Runtime version(s)||v1.8.x, v1.9.x, v1.10.x, and v1.11.x|
|IaaS support||AWS, OpenStack, and vSphere|
To install and use a9s LogMe for PCF, you must install the following products and tiles:
- Elastic Runtime, v1.7 or later
- a9s Consul DNS for PCF, v1.0.0 or later
- a9s BOSH for PCF, v1.0.0 or later
For installation instructions, see Installing and Configuring a9s LogMe for PCF.
The anynines team can help you get started and succeed with a9s LogMe for PCF. Technical support, including a service-level agreement, is available with a commercial license.
If your company has specific LogMe administration policies or configuration best practices, the anynines team is happy to incorporate them. Third-party LogMe support organizations are also welcome to assist.
Contributions are welcome and will be investigated by the anynines team. Please send any bugs, feature requests, or questions to email@example.com.
Contact our sales team to learn more about commercial licenses and support.