About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
AWS Fargate Monitoring
AWS Fargate Monitoring is fundamentally different from monitoring a typical cloud computing or application environment. AWS Fargate does not allow agents to be deployed on the actual host, as is typically done for monitoring purposes. To monitor applications and services within containers on AWS Fargate, the agent must be integrated into the container image.
To meet the various challenges of monitoring AWS Fargate, Instana is leveraging the knowledge gained with our best-in-class AWS Lambda monitoring technology. Instana collects a distributed trace for every request of every ECS Task. Instana’s distributed tracing is easily incorporated in the Docker-image at build-time ensuring there are never unmonitored applications. Traces are correlated across ECS clusters, Amazon EC2, AWS Lambda, AWS Fargate and any other technology monitored by Instana, so there is always an end-to-end view of every application request. Each trace is also made viewable and searchable with Instana’s Unbounded Analytics.
Instana AWS Fargate Monitoring comes with the following capabilities:
Instana AWS Fargate Monitoring comes with the following capabilities:
Application Performance and AWS Fargate Monitoring
When using AWS Fargate (link resides outside ibm.com) it is important to properly monitor the performance of applications but getting the full visibility needed can be difficult as it is challenging to monitor workloads without managing or controlling the orchestration. Current Application Performance Monitoring (APM) tools generally provide trace sampling and often only partial traces. This approach does not suffice when monitoring cloud-native environments that automatically scale, like AWS Fargate.
AWS itself also has a monitoring solution for AWS Fargate, AWS X-Ray (link resides outside ibm.com). X-Ray provides a distributed tracing solution that monitors applications running on AWS Fargate. With AWS X-Ray users can trace requests as they travel through the application while getting visibility into the application’s underlying components. AWS X-Ray helps developers analyze and debug problems within AWS environments. However, when it comes to deciding if it is the right monitoring solution some further considerations are required.
Cost: As always, when considering a solution, cost is an important factor to take into account. AWS X-Ray is billed on a per traced call basis. So depending on the amount of traffic that is being pushed through the applications, this can quickly become a non-trivial cost. There are also extra charges to analyze the traces after they are collected.
Limited to AWS: It is also important to take into account the entirety of the environment or environments the applications run on. AWS X-Ray is limited to tracing services that are being provided by, or are within, AWS. As such, AWS X-Ray has limited value in hybrid environments. Companies that have applications and services that span multiple environments need to consider the impact of having multiple monitoring solutions to gain the full visibility needed.
