aws-observability / aws-o11y-recipes Goto Github PK

Submitting an issue to convert https://aws.amazon.com/blogs/mt/auto-scaling-amazon-ec2-using-amazon-managed-service-for-prometheus-and-alert-manager/ in the Observability recipes

• Glossary of services
• How to write recipe (link to main README)
• How to find stuff

A recipe on how to use Prometheus/Alertmanager/AMP to monitor dev/build infra components like GitLab, Jira, and Confluence, getting alerts when they are down.

Going through the guide, it works as intended. However, I suggest a couple of minor enhancements:

• Setting your AWS region as an environment variable is done twice in two different variables; we can reduce this to just one
• Removing step 3 of the ADOT Collector setup (<YOUR_ACCOUNT_ID>unused in yaml)

https://aws.amazon.com/blogs/opensource/migrating-x-ray-tracing-to-aws-distro-for-opentelemetry/

Talk about different exporters, extensions and patterns available to setup monitoring on ECS

Based on Using OpenTelemetry Collector for Logs on K8s, create a recipe for EKS.

Regarding Exporting CloudWatch Metric to Amazon Managed Service for Prometheus
It makes more sense to directly send metrics from Cloudwatch metric streams directly to Amazon Managed Service for Prometheus.
Or add Amazon Managed Service for Prometheus as a destination for Firehose.

On this recipe page:
https://aws-observability.github.io/aws-o11y-recipes/recipes/amg-automation-tf/

The 3rd prerequisite says:
"You have to have Amazon Managed Prometheus workspace..."
The service name should be Grafana.

Showing the Prometheus Operator in action with Amazon Managed Service for Prometheus:

• Set up with AMP
• How to migrate local/DIY rules and alert manager to AMP

Use AMP and AMG to monitor Jenkins environment running on EKS

Please kindly help adding “AWS App Runner” icon in “Compute Unit” dimension row: https://github.com/aws-observability/aws-o11y-recipes/blob/main/docs/images/o11y-space.png

Show how to configure the SAML setting of a Managed Grafana workspace with the ADFS Single Sign-On solution.

In Amazon Managed Grafana , show how to alert based on Prometheus source (SLO/SLI use case for example) with SNS, for:

• EKS
• ECS
• EC2 monolith

ho11y App's Dockerfile is missing the follow statements so the docker build fails for goproxy wilth following error

go: github.com/bitly/[email protected]: git init --bare in /go/pkg/mod/cache/vcs/460f3a74af59eb3467f80d2023ccd36e4efe950fa38720c01021f858760cc232: exec: "git": executable file not found in $PATH
The command '/bin/sh -c CGO_ENABLED=0 go build -a -ldflags '-extldflags "-static"'' returned a non-zero code: 1

Please add the below after line 1 in ho11y's Dockerfile to get through this error :

 RUN go env -w GOPROXY=direct
 RUN apk add --no-cache git

Turn Introducing Amazon EKS Observability Accelerator into a recipe and:

1. Make sure that aws-ia/terraform-aws-eks-blueprints#617 is merged first
2. Call out how to deal with Error: could not download chart: issue (this is a known TF Helm provider issue, one needs to manually helm repo remove xxx and helm repo update to fix it)

As an Observability engineer, I would like to be able to filter metric results using resource tags to be able to have group elements form the same resource
example: cpu utilization of all ec2 instances with the tag team:teamX

Use AMG to monitor workloads running on an Azure platform

Add recipe for AWS managed Grafana workspace URL to be pointing to a custom URL/Domain. I have been trying this with cloudfront sitting with an alternate domain name but keep getting the error corresponding relay isn't found
It will be nice if someone can add that as it be useful for other people too

Some of the documentation, such as the EKS on EC2 and EKS on Fargate --> AMP docs, use eu-west-1 as a default region. I suggest more general language like <YOUR_AWS_REGION> be used instead.

When I do a go build -o main main.go on https://github.com/aws-observability/aws-o11y-recipes/blob/main/sandbox/CWMetricStreamExporter/lambda/main.go I get the following error on a Mac with go 1.18.2:

» go build -o main main.go                                                  
# command-line-arguments
./main.go:82:15: cannot use currentLabels (variable of type []*prompb.Label) as type []prompb.Label in struct literal
./main.go:246:15: cannot use timeseries (variable of type []*prompb.TimeSeries) as type []prompb.TimeSeries in struct literal
-----------------------------------------------------------------------------------------------------------------------------

In the main README.md add instructions on how to set up mkdocs for local preview and share conventions (where does a recipe go, how to link up from one or more top-level entries, images, etc.).