-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(datastreams): botocore - log warning on kinesis stream metadata not found #11647
Conversation
…s/dsm-kinesis-error-handling
|
@emmettbutler Is this good to add to the merge queue? |
@burnsdy looks like it to me! |
/merge |
Devflow running:
|
BenchmarksBenchmark execution time: 2024-12-11 16:55:05 Comparing candidate commit 02fa057 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 394 metrics, 2 unstable metrics. |
/merge |
Devflow running:
|
/merge |
Devflow running:
|
/merge |
Devflow running:
|
For Data Streams Monitoring with AWS Kinesis, the map on the DSM page will break if
StreamARN
isn't provided to the Kinesisget_records
call. This is because dd-trace-py requires theStreamARN
when generating a consume checkpoint for an in-edge in the data streams map. If there's no consume checkpoint, the data streams map incorrectly renders as two graphs instead of one connected graph.However, the Kinesis
get_records
API listsStreamARN
as an optional parameter (see docs). If it isn't provided, dd-trace-py only outputs a debug-level log, and the DSM map is rendered incorrectly. This PR ensures dd-trace-py outputs a warning that is more visible to the developer.This PR can be closed if the current state of error handling is acceptable, since I don't know if there are restrictions on logging warnings for this repo. The warning helps to debug the broken DSM map, which is time-consuming to debug otherwise.
No testing updates are required since there isn't a unit test file for this specific module.
Checklist
Reviewer Checklist