EXPORT CLOUDWATCH METRICS TO PROMETHEUS CODE
The code snippets shown above instrument three different metrics to track the number of visitors to each page and overall visitors in general using an open source Prometheus client library. Private static readonly Counter ProductsPageHitCounter = Metrics.CreateCounter("PrometheusDemo_ProductsPage_Hit_Count", "Count the number of hits to Products Page") Private static readonly Gauge SiteVisitorsCounter = Metrics.CreateGauge("PrometheusDemo_SiteVisitors_Gauge", "Site Visitors Gauge") Īs well as the ProductsController.cs file: // Prometheus metric: Private static readonly Counter HomePageHitCounter = Metrics.CreateCounter("PrometheusDemo_HomePage_Hit_Count", "Count the number of hits to Home Page")
Instrument app for custom metricsįirst, clone the sample application from aws-samples/amazon-cloudwatch-prometheus-metrics-sample and have a look at the HomeController.cs file: // Prometheus metrics: We will do this using the CloudWatch Prometheus agent with a custom configuration. In this following setup we will instrument an ASP.NET Core application using Prometheus client libraries with the goal to expose custom metrics and ingest these metrics into CloudWatch. In action: using Prometheus in an ASP.NET app The screenshot below shows the built-on dashboard for AWS AppMesh workload hosted on an ECS cluster with CloudWatch Container Insights enabled. You can also add the widgets shown on the built-on dashboards to a custom dashboard of your choice as well by simply clicking on the Add to dashboard button. Using this, you are now not only able to quickly setup Prometheus metric monitoring on CloudWatch but also get deeper insights into these workloads without having to create a dashboard from the scratch. You can also make use of the out-of-the box dashboards provided by CloudWatch Container Insights for workloads such as AWS AppMesh and Java/JMX. You benefit from a rich open source ecosystem in terms of exporters and have the freedom of choice where, how, when to consume your metrics based on an open industry standard. In addition, more generally speaking, using Prometheus enables you a smooth and flexible migration path from on-premises deployments. Especially for EKS, easily set up control plane monitoring.The ability to configure, add and drop new metrics and dimensions.The ability to create alarms with a deep integration with other AWS services such as SNS.You get a range of out-of-the-box dashboards.No matter the container orchestrator you’re running your containerized microservices on, be it Amazon EKS or ECS, using the CloudWatch CI support for Prometheus metrics offers a number of benefits, some of which we will demonstrate in the following: Benefits of Prometheus metrics with CloudWatch
EXPORT CLOUDWATCH METRICS TO PROMETHEUS HOW TO
Before we dive into the topic of how to use Prometheus metrics in CloudWatch from ECS, let us first discuss why you would want to do that. The community around Prometheus has found interesting use case: from monitoring temperature on a Raspberry Pi to its role in service meshes we encourage you to learn more about its origins and applications areas.įor a general introduction to CloudWatch Container Insights (CI) monitoring for Prometheus, we recommend perusing our docs. While Prometheus has its root in the Kubernetes ecosystem, it’s by no means limited to it. Now that we made this feature generally available we explore its benefits in greater detail and show you how to use Prometheus in the context of Amazon ECS, our native container orchestrator. In Using Prometheus Metrics in Amazon CloudWatch we showed you how to use the beta version of the Amazon CloudWatch supporting the ingestion of Prometheus metrics.
Imaya Kumar Jagannathan, TP Kohli, and Michael Hausenblas
0 kommentar(er)
