Skip to main content
Version: Develop

Known Issues

This page describes concerns, limitations to be considered when allocating resources for the a9s Prometheus plans, and other known issues.

Limitations​

a9s Prometheus is still in beta, please note the following restrictions:

  • Encryption in transit is not available for client-side nor internal communication
  • The configuration of Prometheus, Graphite and Grafana are not backed up in any way
  • Only non-clustered instances are available
  • a9s Prometheus doesn't come with an a9s Service Dashboard, as there is no backup functionality. This means that:
    • The Prometheus dashboards can be opened via a simple landing page, the access of which requires authentication like any other dashboard
    • Basic system metrics are not available as there is no actual link between the landing page and the backend components to make that possible
  • Metrics and Logs are not available for a9s Prometheus' instance components
  • The Service Instances are not protected with a9s Parachute, which means that neither the ephemeral nor the persistent disk are protected from overflow/overuse