Amazon CloudWatch Agent заопенсорсился:

https://github.com/aws/amazon-cloudwatch-agent

Он теперь входит в Amazon Linux 2, где ставится командой:

sudo yum install amazon-cloudwatch-agent

#CloudWatch #Amazon_Linux

Вообще, нужно отметить, что в этом году CloudWatch серьёзно прокачался:

• объединение алярмов
• интегрировался с AWS Chatbot
• заработал быстрей
• увеличил квоты
• логи для Динамы
• CloudWatch Synthetics
• добавилась поддержка для Blockchain, Media сервисов, DataSync , DocumentDB, AppFlow
• логи в VS Code

А из самых недавних это поддержка Prometheus и особенно, если пропустили — возможность шарить дашборды любому встречному.

То есть теперь можно дать доступ к вашим графикам-логам любому человеку (без AWS аккаунта) — просто как публичная ссылка, логин-пароль по почте или через SSO. Это очень круто — можно давать доступ руководству на время или постоянно простым копированием ссылки.

Опенсорсивание лишь показывает нацеленность на контейнеры и попытку конкурировать с популярными продуктами в этой области. И теперь при выборе решения для логирования-мониторинга кандидатура CloudWatch смотрится совсем в другом свете.

А ведь год ещё не закончился.

#CloudWatch

Автоматизация настройки CloudWatch алярмов для виртуалок с помощью SSM:

https://aws.amazon.com/blogs/mt/automating-amazon-cloudwatch-alarms-with-aws-systems-manager/

#SSM #CloudWatch

​​Шаринг CloudWatch дашбордов:

https://aws.amazon.com/blogs/mt/communicate-monitoring-information-by-sharing-amazon-cloudwatch-dashboards/

Крутая фича, появившаяся в 2020-м году. Очень стоит как минимум попробовать. Для кого-то возможность так легко шарить графики (и логи тоже, кстати) может стать весомым аргументом в пользу использования CloudWatch как основного средства логирования/мониторинга/алертинга.

#CloudWatch

CloudWatch метрики прямо в терминале:

https://github.com/mhlabs/awscii-cli

CLI tool that lets you render predefined AWS graphs in ASCII art using asciichart.
AWS services:
• Lambda
• DynamoDB
• API Gateway

#CloudWatch

Как мониторить (и рестартовать) сервисы на EC2 инстансе с помощью CloudWatch и SSM:

https://aws.amazon.com/blogs/mt/detecting-remediating-process-issues-on-ec2-instances-using-amazon-cloudwatch-aws-systems-manager/

You can use the Amazon CloudWatch agent procstat plugin, which continuously watches specified processes and reports their metrics to Amazon CloudWatch. After the data is in Amazon CloudWatch, you can associate alarms to trigger actions like notifying teams or remediations like restarting the processes, resizing the instances, and so on.

#CloudWatch #SSM

​​CloudWatch Resource Health - мониторинг приложений, запущенных на EC2:

https://aws.amazon.com/blogs/mt/introducing-cloudwatch-resource-health-monitor-ec2-hosts/

Resource Health provides a centralized view of your EC2 hosts by performance dimensions such as CPU or memory utilization. You can use Resource Health to slice and dice hosts using filters such as instance type, instance state, or security groups. It enables a side-by-side comparison of a group of EC2 hosts and provides granular insights into an individual host.

#CloudWatch

AWS Cloudwatch Centerlized Monitoring

https://ripon-banik.medium.com/aws-cloudwatch-centerlized-monitoring-41f7032721d

#aws #cloudwatch #monitoring

Amazon CloudWatch Evidently – инструмент для A/B тестирования:

https://aws.amazon.com/blogs/aws/cloudwatch-evidently/

Тестировать можно не только front-end, но также back-end, мобильные и любые другие приложения. Поддерживаемые языки:
C++, Go, Java, JavaScript (and Typescript), .Net, NodeJS, PHP, Python, and Ruby.

Цена на CloudWatch Evidently:
First time free trial includes 3 million Evidently events and 10 million Evidently analysis units per account

#CloudWatch

​​CloudWatch RUM (Real-User Monitoring):

https://aws.amazon.com/blogs/aws/cloudwatch-rum/

Такой себе вариант Google Analytics от AWS для отработки ошибок и производительности на клиентской стороне, т.е. у юзеров (потому Real-User).

#CloudWatch

​​How to send repeated notifications for CloudWatch Alarms:

https://aws.amazon.com/blogs/mt/how-to-enable-amazon-cloudwatch-alarms-to-send-repeated-notifications/

1️⃣ CloudWatch alarm is triggered and goes into the ALARM state.
2️⃣ CloudWatch alarm sends the first alarm notification to the associated SNS alarm actions.
3️⃣ CloudWatch Alarms service sends an alarm state change event which triggers the EventBridge rule.
4️⃣ With a match event, the EventBridge rule invokes the Step Function target.
5️⃣ Once the Step Function starts execution, it first enters a Wait state.
6️⃣ The Step Function enters the Lambda Invocation task. The Lambda invocation task:
▫️ Checks if the alarm has the specific tag key and value (e.g., RepeatedAlarm:true). If not, the function exits
▫️ Checks the alarm’s current state by performing a DescribeAlarms API with the alarm name.
▫️ Publishes the existing alarm’s status returned from the DescribeAlarms API call to all the SNS topics subscribed on the alarm
▫️ Returns the alarm’s current state together with the original received event back to the Step Function.
7️⃣ The Choice state checks the alarm state returned by the Lambda function and directs the workflow to go back to the Wait state if the alarm state is ‘ALARM’ otherwise it ends the step function’s execution.
8️⃣ The repeated notification for an alarm within the workflow above stops when:
▫️ The alarm transitions to a non-ALARM state.
▫️ The alarm is deleted.
▫️ A specific tag is removed from the alarm.

#CloudWatch

CloudWatch Container Insights for EKS Fargate using ADOT (AWS Distro for OpenTelemetry):

https://aws.amazon.com/blogs/containers/introducing-amazon-cloudwatch-container-insights-for-amazon-eks-fargate-using-aws-distro-for-opentelemetry/

▫️ This blog presented an overview of the design of the ADOT Collector for EKS Fargate with support for CloudWatch Container Insights and demonstrated its deployment and metrics collection from workloads on an EKS Fargate cluster.
▫️ A single collector instance is able to discover all the worker nodes in an EKS cluster through the use of Kubernetes service discovery and collect metrics from them by using the Kubernetes API server as a proxy for the kubelet on worker nodes.
▫️ EKS customers will now be able to collect system metrics such as CPU, memory, disk, and network usage from workloads that are deployed to an EKS Fargate cluster and visualize them in CloudWatch dashboards, providing the same experience as CloudWatch agent.

#CloudWatch

​​Weekly Summary on AWS (February 20-26)

🔸 Amplify + The Authenticator UI Library for Flutter
🔸 AppSync + custom response headers
🔸 App Mesh + Agent for Envoy
🔸 App Runner + Java
🔸 Billing + Payment Profiles
🔸 CloudWatch Agent
➖ Configurable Log Group Retention
➖ NVIDIA GPU Metrics
🔸 Connect Customer Profiles + high-volume ingestion of customer data
🔸 EC2 Auto Scaling Warm Pools + hibernating and returning instances to Warm Pools on scale-in
🔸 Firewall Manager + AWS Network Firewall Centralized Deployment Model
🔸 Glue Job Run Insights
🔸 Glue DataBrew + choose single or multiple output files
🔸 Glue Schema Registry + Protobuf
🔸 Lambda + .NET 6
🔸 QuickSight’s new community hub
🔸 RDS for MariaDB + IAM authentication
🔸 Redshift + PIVOT and UNPIVOT SQL operators
🔸 S3 + additional checksum algorithms
🔸 SageMaker + 322 popular ML models
🔸 SAM CLI + TypeScript
🔸 Transfer Family + enhancements to workflows
🔹 NICE DCV version 2022.0 and Web Client SDK version 1.1.0

#AWS_week

​​🆕 CloudWatch Internet Monitor:

https://aws.amazon.com/blogs/aws/cloudwatch-internet-monitor-end-to-end-visibility-into-internet-performance-for-your-applications/

● Internet Monitor uses the connectivity data that we capture from our global networking footprint to calculate a baseline of performance and availability for internet traffic. This is the same data that we use at AWS to monitor our own internet uptime and availability. With Internet Monitor, you can gain awareness of problems that arise on the internet experienced by your end users in different geographic locations and networks.
● There is no need to instrument your application code. You can enable the service in the CloudWatch section of the AWS Management Console and start to use it immediately.

#CloudWatch

​​🆕 CloudWatch Cross-Account Observability:

https://aws.amazon.com/blogs/aws/new-amazon-cloudwatch-cross-account-observability/

To enable cross-account observability, CloudWatch has introduced the concept of monitoring and source accounts:
◘ A monitoring account is a central AWS account that can view and interact with observability data shared by other accounts.
◘ A source account is an individual AWS account that shares observability data and resources with one or more monitoring accounts.

You can configure multiple monitoring accounts with the level of visibility you need. CloudWatch cross-account observability is also integrated with Organizations.

💳 Cross-account observability in CloudWatch comes with no extra cost for logs and metrics, and the first trace copy is free. 👍

#CloudWatch

Ещё 0.44 дашборды и придётся платить!

#CloudWatch #Budgets #FreeTier

6️⃣ CloudWatch Agent можно установить в виртуалку прямо из AWS Console. Но это не точно.

Коллеги, подскажите, у кого-то работает сие чудо?

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-and-configure-cloudwatch-agent-using-ec2-console.html#install-and-configure-cw-agent-procedure

Всю жизнь мечтал. Вопрос каждого первого начинающего работать с AWS — а где нагрузка по процессам и свободное место на диске? Неужели свершилось?

Кто пропустил, краткая история предыдущих серий CloudWatch Agent.

1️⃣ Ничего не было, выживали мониторили, как могли.
2️⃣ Скрипт на Perl, ура, спасибо, что не Fortran! Установка ручками через SSH.
3️⃣ Везде Docker. В деревне Гадюкино CloudWatch Agent — скрипт на Perl, установка через SSH.
4️⃣ Везде Kubernetes и Serverless, в CloudWatch Agent — скрипт на Perl, установка через CloudFormation.
5️⃣ CloudWatch Agent переписали на Go, установка через SSM.

#CloudWatch