During incidents, engineers need to filter traces by districtId and permitType. What should they add in the application?
Select an answer to reveal the explanation.
Short Explanation
Annotations are the sticky notes X-Ray can index. Stamp districtId and permitType so incident filters actually find the traces you care about.
Full Explanation
During incidents, engineers who must filter traces by districtId and permitType should add AWS X-Ray annotations for those fields. Annotations are indexed key-value pairs suitable for filter expressions, unlike arbitrary metadata that may not support search the same way. Municipal incidents often start with "which district and permit type are failing?" and annotations make that queryable.
Storing districtId only in an S3 inventory CSV outside any trace prevents online incident filtering in X-Ray.
Putting permitType solely in Cost Explorer tags never helps trace search during an outage.
Disabling X-Ray annotations because "filters work only on account IDs" is incorrect and removes useful indices.
Exam caveat: Use annotations for indexed filterable fields; use metadata for additional non-indexed detail when needed.
Operational check: Add districtId and permitType annotations on the permit API traces, run a filter during a game-day exercise, and confirm on-call can isolate a district outage within the X-Ray console. Keep the civic/municipal context in mind: multi-district cities need rapid geographic and permit-type slicing during incidents. Document the finding in the municipal incident ticket so the next on-call engineer inherits evidence rather than folklore.