a9s LogMe
a9s LogMe service is deprecated and it will become unsupported soon, it will be replaced by a9s LogMe2, for more information on how to migrate, please see our migration guide
a9s LogMe 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. Common to all a9s Data Services are the comprehensive plans delivering on-demand scaling from small single nodes to big node clusters. a9s LogMe service instances can be deployed via Apps Manager or the Cloud Foundry Command Line Interface.
Overview
By utilising a one VM per node architecture a9s LogMe secures its processes performance, reliability, and integrity. This layered approach serves as reliable mitigation against "noisy neighbor" problems, and grants the controls needed for applying common security practices (e.g. application security categorization).
Current Features
a9s LogMe includes the following key features:
| Feature | Description |
|---|---|
| On-demand provisioning | Deploy and upgrade to meet demand simply with the Cloud Foundry CLI or Apps Manager |
| Layered security | VM based isolation promoting alignment with enterprise security requirements |
| Network isolation | 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. |