- AWS Solutions Library›
- Guidance for Monitoring High-Cardinality Telecom Metrics on AWS
Guidance for Monitoring High-Cardinality Telecom Metrics on AWS
Overview
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Well-Architected Pillars
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
CloudWatch collects and displays real-time logs, metrics, and event data in automated dashboards to streamline your infrastructure and application maintenance. Lambda is used to enhance the capabilities in CloudWatch dashboards with custom widgets.
CloudWatch logs are compliant with Payment Card Industry (PCI) and Federal Risk and Authorization Management Program (FedRAMP). CloudWatch is also integrated with AWS Identity and Access Management (IAM) so you can control which users and resources can access your data, and set permissions for how your data is accessed. You can also define data protection policies to discover and protect sensitive data logged by systems and applications. Lastly, data in this Guidance is encrypted at rest and in transit.
To keep your applications running smoothly, use CloudWatch to gain system-wide visibility into resource utilization, application performance, and operational health. CloudWatch is a fundamental service that equips you to collect logs, gather metrics, and send notifications when thresholds are crossed or significant events occur.
CloudWatch is a monitoring and observability service that provides you with both data and actionable insights. It helps you monitor your workloads so you can better respond to changes in performance of your systems and processes.
The CloudWatch embedded metric format allows you to asynchronously generate custom metrics in the form of logs that are written to CloudWatch logs. CloudWatch then automatically creates an aggregated metric, which in turn provides a cost-effective way to monitor resources. Additionally, by using the embedded metric format, the cost of the PutMetricData API is removed.
CloudWatch streamlines data storage and eliminates the need to call the PutMetricData API to generate metrics, eliminating the need for additional compute. CloudWatch logs are also stored and estimated to be 15% of log volume ingested (due to compression). To further minimize your required resources, you can set a retention policy on individual log groups.
Implementation Resources
Disclaimer
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages