- restrict prometheus to pulling metrics, not accessing api
- create SecurityGroup that targets should have attached to make reachable
- configure BlackBox outside of main config
x curl --retry 120 --retry-delay 1 # -qsS4f x install-docker s/service/systemctl/
-
restrict AmazonEC2ReadOnlyAccess
- identify what's needed by Prometheus
- ELB SG Egreee allow all to target:InstanceSecurityGroup
-
add
--hard-links
to rsync -
use long args for all commands
-
restrict ec2_sd to same VPC
-
keypair-create can upload existing key if it finds or is given one
-
PushGateway
-
encrypt (KMS?) passwords
-
document how to use with ec2 discovery
- document how to get security group
- add security group to stack outputs
- document how to get security group
-
durable
- separate EBS volume that gets mounted
- how do we make grafana configs/data durable?
- work out how to make it not replace instance when AmazonLinux2 ami changes
{ "ParameterKey": "ImageId", "ParameterValue": "/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2", - "ResolvedValue": "ami-04481c741a0311bbb" + "ResolvedValue": "ami-0c3228fd049cdb151" },
-
sd_ec2 should contain a label with stack name and maybe instance-id
-
how to keep local configs
- fork and remove from .gitignore?
-
grafana
- document how to save dashboard as JSON
- document sharing grafana graph without login
- can we give readonly access without login?
- whitebox: service claims to be working
- blackbox/synthetic: we can actually use service
- passive: we see others are using the service
- how to use grafana when we have prometheus in each AZ?