-
Notifications
You must be signed in to change notification settings - Fork 30
Traffic Capture Verification
Greg Schohn edited this page Sep 10, 2024
·
6 revisions
- Traffic Capture Proxy deployed in ECS (not within cluster nodes)
- Migration Console and Traffic Replayer have been deployed
- Navigate to Migration ECS Cluster in AWS Console
- Navigate to Capture Proxy Service
- Verify > 0 desired count and running
- if not, update service to increase to at least 1 and wait for startup
- Within "Load balancer health" on "Health and Metrics" tab, verify all targets are reporting healthy
- This means the ALB is able to connect to the source cluster through the capture proxy
- Navigate to the Migration Console Terminal
- Execute
console kafka describe-topic-records
- Wait 30 seconds for another elb health check to be recorded
- Execute
console kafka describe-topic-records
again, Verify RECORDS increased between runs - Execute
console replay start
to start the replayer - Run
tail -f /shared-logs-output/traffic-replayer-default/*/tuples/tuples.log | jq '.targetResponses[]."Status-Code"'
to confirm that the Kafka requests were sent to the the target and that it responded as expected.
- if responses don't appear
- check that the migration-console can access the target cluster by running
./catIndices.sh
, which should show indices on the source and target. - confirm that messages are still being recorded to Kafka.
- check for errors in the replayer logs ("/migration/STAGE/default/traffic-replayer-default") via CloudWatch
- check that the migration-console can access the target cluster by running
- (Reset) Update Traffic Capture Proxy service desired count back to original value in ECS
- If source cluster requires auth, will not be able to verify beyond receiving 401/403 status code for ALB healthchecks
- Verify Source Cluster allows traffic ingress from Capture Proxy Security Group
- Navigate to Traffic Capture Proxy ECS Tasks to investigate failing tasks
- Change "Filter desired status" to "Any desired status" in order to see all tasks and navigate to logs for stopped tasks
Cut a GitHub issue referencing page and assigning to
owner: @AndreKurait
Encountering a compatibility issue or missing feature?
- Search existing issues to see if it’s already reported. If it is, feel free to upvote and comment.
- Can’t find it? Create a new issue to let us know.
- Migration Assistant Overview
- Is Migration Assistant Right for You?
- Existing Data Migration - Quick Start Guide
- A. Snapshot Creation Verification
- B. Client Traffic Switchover Verification
- C. Traffic Capture Verification
- D. System Reset Before Migration