Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
vijayansarathy authored Feb 28, 2021
1 parent 94aae1b commit 743c79f
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,12 +26,14 @@ At a high level, we will be following the steps outlined below for this solution
### Deploy

Requires an ECS cluster. For deploying the Prometheus Node Exporter, a cluster with EC2 instances is required. All deployment artifacts are under the [deploy](https://github.com/aws-samples/prometheus-for-ecs/tree/main/deploy) directory. The deployment comprises the following components:
- An ECS task comprising the Prometheus server, AWS Sig4 proxy and the service discovery application containers</li>
- A mock web application that is instrumented with Prometheus client library and exposes an HTTP endpoint */work*. The application has an internal load generator that send randomized traffic to the HTTP endpoint. The service exposes a [Counter](https://prometheus.io/docs/concepts/metric_types/#counter) named *http_requests_total* and a [Histogram](https://prometheus.io/docs/concepts/metric_types/#histogram) named *request_durtaion_milliseconds*
- Prometheus Node Exporter to monitor system metrics from every container instance in the cluster. This service is deployed using [*host* networking mode](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#network_mode) and with the daemon scheduling strategy. Note that we can’t deploy the Node Exporter on AWS Fargate because it does not support the daemon scheduling strategy.
- An ECS task comprising the Prometheus server, AWS Sig4 proxy and the service discovery application containers
-
- A mock web application that is instrumented with Prometheus client library and exposes an HTTP endpoint */work*. The application has an internal load generator that sends client requests to the HTTP endpoint. The service exposes a [Counter](https://prometheus.io/docs/concepts/metric_types/#counter) named *http_requests_total* and a [Histogram](https://prometheus.io/docs/concepts/metric_types/#histogram) named *request_durtaion_milliseconds*
-
- Prometheus Node Exporter to monitor system metrics from every container instance in the cluster. This service is deployed using [*host* networking mode](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#network_mode) and with the daemon scheduling strategy. Note that we can’t deploy the Node Exporter on AWS Fargate because it does not support the daemon scheduling strategy.


The deploment scripts assume that the underlying ECS cluster was created using the ecs-cluster.yaml under the deploy directory. Create the cluster with the following command:
The deploment scripts assume that the underlying ECS cluster was created using the [ecs-cluster.yaml](https://github.com/aws-samples/prometheus-for-ecs/blob/main/deploy/ecs-cluster.yaml) CloudFormation template. Create the cluster with the following command:
```
VPC_STACK_NAME=ecs-stack
VPC_TEMPLATE=ecs-cluster.yaml
Expand Down

0 comments on commit 743c79f

Please sign in to comment.