Skip to main content
Version: Latest

Resource Considerations

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

Since a9s LogMe2 includes an OpenSearch cluster (or single), all limitations for a9s Search apply to this Data Service as well.

Dependency on Trusted Certificates​

In order to be able to use the TLS syslog drain functionality and for the OpenSearch Dashboards to be reachable, you must configure either a CA or a wildcard certificate.

These certificates must be trusted by Cloud Foundry as well.

This limitation also extends to the user provided certificates as the Certificate Authority (CA) used to sign them must be trusted by Cloud Foundry.

Fluentd​

Buffers​

Traditionally, Fluentd has used memory buffers for buffering data. While memory buffers are fast and efficient, they come with the risk of losing data in case of a system failure. In order to mitigate this risk, we have decided to switch to file buffers.

Bundled Plugins​

caution

This limitation applies both to the OpenSearch and OpenSearch Dashboards plugins.

a9s LogMe2 deliberately limits the available plugins, including the Bundled Plugins, to ensure integrity, stability, and usability of the Data Service. This set of plugins is static and cannot be extended, nor modified, by the Platform Operator.

The available OpenSearch plugins are:

  • opensearch-alerting.
  • opensearch-index-management.
  • opensearch-job-scheduler.
  • opensearch-notifications.
  • opensearch-notifications-core.
  • opensearch-security.
  • repository-azure.
  • repository-s3.

The available OpenSearch Dashboards plugins are:

  • alertingDashboards.
  • notificationsDashboards.
  • securityDashboards.