jbrechtel/willfullyobtuse.com
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Some new posts

Browse Source
This commit is contained in:
James Brechtel
2024-10-03 20:59:01 -04:00
parent 7b1899a010
commit 9f533ffd1a
7 changed files with 126 additions and 285 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
aws-metric-filters.org
View File

@@ -24,18 +24,14 @@ know about is AWS CloudWatch Metric Filters. If you're already on AWS
then you should consider these because it requires only that your
application logs to CloudWatch.
If you're on ECS then the
[[https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html][awslogs]]
log driver for Docker gets you that nearly for free. By "free" I mean
that your application itself can have /zero/ dependencies on AWS
services and not require any AWS credentials or libraries to start
pumping out metrics that you can visualize, alert on and record over
time.
If you're on ECS then the [[https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html][awslogs]] log driver for Docker gets you that
nearly for free. By "free" I mean that your application itself can
have /zero/ dependencies on AWS services and not require any AWS
credentials or libraries to start pumping out metrics that you can
visualize, alert on and record over time.
The
[[https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/MonitoringLogData.html][AWS
docs]] themselves offer the canonical reference for configuring these so
I won't go into detail here.
The [[https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/MonitoringLogData.html][AWS docs]] themselves offer the canonical reference for configuring
these so I won't go into detail here.
However, the gist is that for a log filter you define the following
properties
@@ -47,13 +43,8 @@ properties
- And finally a log group to extract the metric values from
After that you just run the application and as the logs roll in the
metric values get pumped out. Then you can
[[https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create-alarm-on-metric-math-expression.html][define
alarms for alerting]] on them,
[[https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Dashboards.html][graph
them]],
[[https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html#policy-creating-alarm-console][define
autoscaling rules]] from them and more.
metric values get pumped out. Then you can [[https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create-alarm-on-metric-math-expression.html][define alarms for alerting]]
on them, [[https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Dashboards.html][graph them]], [[https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html#policy-creating-alarm-console][define autoscaling rules]] from them and more.
To conclude - AWS is big and hairy. While there are benefits to staying
platform agnostic, some AWS services don't require much or any coupling