Skip to main content
Version: 45.0.0

a9s LogMe Resources Considerations

This document describes concerns and limitations to be considered when allocating resources for your a9s LogMe plans.

Since a9s LogMe includes an Elasticsearch cluster (or single), all limitation for a9s Elasticsearch applies to this service as well.

Max Payload Bytes

Kibana can only handle requests with a maximum configured size (server.maxPayloadBytes). The Kibana running on a9s LogMe service instances have maxPayloadBytes configured to use 50% of the total memory on the Kibana instance if the total memory is less than 4GB, and 75% if greater.

The minimum size for maxPayloadBytes on an a9s LogMe service instance is 256MB. Requests bigger than this are rejected.

Backups Limitations

The following limitations are due to the known limitations of a9s Elasticsearch.

Known Limitations of a9s LogMe's Backups
  • The backup process is based on Elasticsearch's Snapshot functionality, this means that:
    • Backups are not encrypted.
      • Due to this, the backup_manager_encryption_key property cannot be set.
    • Backups cannot be downloaded.
    • The storage backend is limited to AWS S3 and Azure; generic S3 API services are not supported.
  • Elasticsearch's default filter plugins are not available.