Filtered Traces for User A in AWS X-Ray | Exam DVA-C01 Answer

Get Filtered Traces for User A | Exam DVA-C01 Answer

Prev Question Next Question

Question

An online educational institute uses a three-tier web application & is using AWS X-Ray to trace data between various services.

User A is experiencing latency issues using this application & the Operations team has asked you to gather all traces for User A.

Which of the following needs to be enabled to get Filtered output for User A from all other traces?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Correct Answer - B.

Annotations are key-value pairs indexed to use with filter expressions.

In the above case, traces for a user A needs to be tracked, for which Annotations can be used along with a Filter expression to find all traces related to that user.

Option A is incorrect as Trace ID will track a request's path through the application & will not be used in filtering messages.

Option C is incorrect as Segment will provide details of resource name, request & work done.

It will not help in filtering messages.

Option D is incorrect as the Tracing Header consists of Root trace ID, Segment ID & sampling decision.

It is not useful for filtering messages.

For more information on Annotations & Filter expressions on AWS X-Ray, refer to the following URL-

https://docs.aws.amazon.com/xray/latest/devguide/xray-concepts.html

To gather all traces for a specific user in a three-tier web application using AWS X-Ray, you need to enable the tracing header. The tracing header is a unique identifier that allows X-Ray to associate all traces that belong to a specific user or request.

AWS X-Ray is a service that allows you to trace and analyze requests as they travel through your application. It provides end-to-end visibility into requests and helps you identify issues such as latency, errors, and other performance problems.

In AWS X-Ray, a trace is a collection of data about a single request as it moves through your application. A trace consists of one or more segments, which are individual components of your application, such as a web server, a database, or an API.

Annotations are metadata that you can attach to segments to provide additional information about them. Annotations are useful for adding context to traces, but they are not required to trace requests.

The segment ID is a unique identifier for each segment in a trace. The segment ID can be used to identify a specific segment within a trace, but it is not useful for filtering traces by user.

The trace ID is a unique identifier for each trace. The trace ID can be used to group all segments in a trace, but it is not useful for filtering traces by user.

In summary, to get filtered output for a specific user in a three-tier web application using AWS X-Ray, you need to enable the tracing header. The tracing header is a unique identifier that allows X-Ray to associate all traces that belong to a specific user or request. Annotations and segment IDs are useful for adding context to traces, but they are not required for tracing or filtering traces by user.