80 docs tagged with "data service"

Before proceeding, it is recommended to read the Introduction page. It covers key concepts such

Configuration Layers

a9s Consul is used for service discovery within the a9s Data Services. It must be in place before deploying any of

a9s-pg is the central PostgreSQL database cluster used by the a9s Data Services Framework to store the state of every

The a9s Backup Service provides backup and restore functionality to all a9s Data Services, and to a9s-pg.

a9s CF Service Guard is an optional component. It is not required for installing the a9s Data Services Framework.

a9s Billing is an optional component. It is not required for installing the a9s Data Services Framework.

The a9s Data Services provide on-demand provisioning of dedicated service instances. Each Service Instance is deployed

Introduction

This document describes conceptual backgrounds as well as detailed procedures used for the disaster recovery process of

This document describes considerations that must be taken into account when allocating resources for the a9s Data

a9s-keyvalue-image

a9s-logme2-image

a9s-mariadb-image

a9s-mariadb-image

a9s-messaging-image

a9s-mongodb-image

a9s-postgresql-image

a9s-prometheus-image

a9s-search-image

This page describes how to access an a9s Service Instance.

a9s LogMe2 has both alerting and notification capabilities, which are enabled through OpenSearch's alertingDashboards

This section describes everything an Application Developer might need to know to use the a9s Data Services. Each a9s

This page describes the Security Groups for the a9s Service Instances.

This page describes the rotation of certificates for the standalone components, such as the a9s Backup Manager or

This page describes concerns, limitations to be considered when allocating resources for the a9s KeyValue plans, and

Object Size Limit

Object Size Limit

This document describes how to discover who is the primary of an a9s MongoDB

An Application Developer has the option to customize their a9s Data Service Instances, and their related Service

As mentioned in Getting Started - Custom Parameters as an end user, an

As mentioned in Getting Started - Custom Parameters as an end user, an

As mentioned in Getting Started - Custom Parameters as an end user, an

As mentioned in Getting Started - Custom Parameters as an end user, an

As mentioned in Getting Started - Custom Parameters as an end user, an

As mentioned in Getting Started - Custom Parameters as an end user, an

As mentioned in Getting Started - Custom Parameters as an end user, an

This document describes the options to fork a service instance from a specific backup or migrate data to a new Service

This document describes how to do data migration between two a9s Messaging Service Instances.

This document describes how to migrate data from an a9s MongoDB Service Instance to another a9s MongoDB Service

Overview

Grafana is part of the a9s Prometheus installations and is used by the Application Developers to visualize metrics from

This topic describes the Grafana Dashboard, which is part of each a9s Prometheus Data Service instance.

This is a step-by-step guide on how to install the a9s Data Services Framework using the anynines-deployment

This page describes concerns, limitations to be considered when allocating resources for the a9s MariaDB plans, and

This page describes concerns, limitations to be considered when allocating resources for the a9s PostgreSQL plans, and

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

This section provides an overview of workarounds for known issues with MariaDB.

This page describes concerns and limitations that should be considered when allocating resources to a9s Messaging plans,

This page describes the lifecycle of all a9s Data Services' Service Instances, as well as how to enact all of its steps.

This page covers important considerations for Platform Operators when transitioning to a9s Prometheus 3. For

This section documents the operational tasks required to run the a9s Data Services.

Template nameVM RoleNodesvCPUsLogging

This guide describes an emergency rollback procedure for a9s Messaging 4 to manually switch to legacy templates. This

RabbitMQ can contain breaking changes with minor updates, especially regarding the application libraries for RabbitMQ.

This page describes usage specific to a9s KeyValue. It builds upon the information provided in

This page describes usage specific to a9s MariaDB. It builds upon the information provided in

This page describes usage specific to a9s Messaging. It builds upon the information provided in

This page describes usage specific to a9s MongoDB. It builds upon the information provided in

This page describes usage specific to a9s PostgreSQL. It builds upon the information provided in

This page describes usage specific to a9s Prometheus. It builds upon the information provided in

This page describes usage specific to a9s Search. It builds upon the information provided in

This page describes the metrics used to monitor state of an a9s KeyValue Service Instance. For further information on

This page describes the metrics used to monitor state of an a9s LogMe2 Service Instance. For further information on how

This page describes the metrics used to monitor state of an a9s MariaDB Service Instance. For further information on

This page describes the metrics used to monitor state of an a9s Messaging Service Instance. For further information on

This page describes some of the available metrics used to monitor state of an a9s MongDB Service Instance. For further

This page describes the metrics used to monitor state of an a9s Search Service Instance. For further information on how

This document describes how to transition from an a9s Prometheus 2 Service Instance to an a9s Prometheus 3 Service

This page describes how to monitor an a9s Service Instance.

This feature is currently in Beta.

The Stop/Start feature, which is currently in Beta, must be enabled by the Platform Operator in order to be used.

This page describes how syslog logs can be streamed to a9s LogMe2. It builds upon the information provided in

Introduction