-
Notifications
You must be signed in to change notification settings - Fork 51
Add IoT Metrics Support #710
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
Open
xiazhvera
wants to merge
23
commits into
main
Choose a base branch
from
iot_metrics_2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+183
−16
Open
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
bf5456e
bind sdk metrics
xiazhvera d3d6352
set aws-c-mqtt to test branch
xiazhvera 21fe38d
bind sdk metrics
xiazhvera 13fe021
update aws-c-common
xiazhvera da7ed31
add SdkMetrics in mqtt5 lib
xiazhvera c167b43
move metrics to client option
xiazhvera 2368721
clean up & lint
xiazhvera c456258
Merge branch 'main' into iot_metrics_2
xiazhvera 03e5d98
update test to use client option
xiazhvera 9a9c89d
Merge branch 'iot_metrics_2' of https://github.com/awslabs/aws-crt-py…
xiazhvera 5f3868c
add metrics for adapter
xiazhvera ec40b81
fix param order
xiazhvera fb81ecc
remove custom metrics test
xiazhvera 0435c7f
update test test_metrics_disabled
xiazhvera 3a7b509
Merge branch 'main' into iot_metrics_2
xiazhvera a21e542
Merge branch 'main' into iot_metrics_2
xiazhvera c51a273
kick ci
xiazhvera 2f31d9d
Merge branch 'iot_metrics_2' of https://github.com/awslabs/aws-crt-py…
xiazhvera a6a3c30
fix set metrics error handling
xiazhvera 0f05a84
address comments
xiazhvera 0b84d10
Merge branch 'main' of https://github.com/awslabs/aws-crt-python into…
xiazhvera ad950b5
allow none metrics
xiazhvera a6982bf
update metrics structure
xiazhvera File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submodule aws-c-mqtt
updated
25 files
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of pulling SdkMetrics in from mqtt5, should we instead implement an mqtt3 version of SdkMetrics? It appears there's precedence for this with the double implementation of OperationStatisticsData. Unsure if this is a good or bad practice but it's one we've previously used. This could also potentially allow us to set different things by default for mqtt3 vs. mqtt5 or it could add confusion and a second place to update things when we make changes...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer not to duplicate the structure across MQTT3 and MQTT5. Maintaining it in two places increases the risk of them going out of sync over time. I realize that's the pattern we used in Python, but I wouldn't consider it a good practice to follow.
If we ever need different defaults for MQTT3 vs. MQTT5, we can always inherit from the base structure at that point.