storytold/terraform-aws-observability-accelerator
2
0
Fork 0
mirror of https://github.com/storytold/terraform-aws-observability-accelerator.git synced 2026-10-09 00:09:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Improve base module docs (#108)

Browse Source 
* Improve base module docs

* Update readme and concepts
- Encourage release tags
- make grafana_api_key as required

* Update wording
This commit is contained in:
Rodrigue Koffi
2023-02-01 18:22:14 +01:00
committed by GitHub
parent 2e3011da1c
commit 19ea8122ad
3 changed files with 42 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts.md
+21 -12
View File
@@ -31,35 +31,44 @@ you need to track changes as part of a Git repository or CI/CD pipeline.
## Base module
The base module allows you to configure the AWS Observability services for your cluster and the AWS Distro for OpenTelemetry (ADOT) Operator as the signals collection mechanism.
The base module allows you to configure the AWS Observability services for your cluster and
the AWS Distro for OpenTelemetry (ADOT) Operator as the signals collection mechanism.
Here is the minimum configuration to have a new Managed Grafana Workspace, Amazon Managed Service for Prometheus Workspace, ADOT Operator deployed for you and ready to receive your data.
This is the minimum configuration to have a new Amazon Managed Service for Prometheus Workspace
and ADOT Operator deployed for you and ready to receive your data.
The base module serve as an anchor to the workload modules and cannot run on its own.
```hcl
module "eks_observability_accelerator" {
source = "aws-observability/terraform-aws-observability-accelerator"
aws_region = "eu-west-1"
# use release tags and check for the latest versions
# https://github.com/aws-observability/terraform-aws-observability-accelerator/releases
source = "github.com/aws-observability/terraform-aws-observability-accelerator?ref=v1.6.1
aws_region = "eu-west-1"
eks_cluster_id = "my-eks-cluster"
# As Grafana shares a different lifecycle, it's best to use an existing workspace.
managed_grafana_workspace_id = var.managed_grafana_workspace_id
grafana_api_key = var.grafana_api_key
}
```
You can optionally reuse existing Workspaces to dissociate their lifecycle from the
Terraform state.
You can optionally reuse an existing Amazon Managed Servce for Prometheus Workspace:
```hcl
module "eks_observability_accelerator" {
source = "aws-observability/terraform-aws-observability-accelerator"
aws_region = "eu-west-1"
# use release tags and check for the latest versions
# https://github.com/aws-observability/terraform-aws-observability-accelerator/releases
source = "github.com/aws-observability/terraform-aws-observability-accelerator?ref=v1.6.1
aws_region = "eu-west-1"
eks_cluster_id = "my-eks-cluster"
# prevents creation of a new Amazon Managed Prometheus workspace
enable_managed_prometheus = false
# reusing existing Amazon Managed Prometheus Workspace
managed_prometheus_workspace_id = "ws-abcd123..."
# prevents creation of a new Amazon Managed Grafana workspace
enable_managed_grafana = false
managed_prometheus_workspace_id = "ws-abcd123..."
managed_grafana_workspace_id = "g-abcdef123"
grafana_api_key = var.grafana_api_key