-
Notifications
You must be signed in to change notification settings - Fork 45
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
Greengrass data usage #1663
Comments
Hi, on rpi, it's possible to use We need some more information to understand what's going on with the traffic.
|
The carrier really doesnt get specific -- its just a large monthly charge :) So, I'm wondering how to sort of 'profile' what is going on or whether greengrass has some way or report to help tell me the size of all data travelling back and forth to validate the carrier charge? |
So I am experimenting with Wireshark. So far no real luck -- I'm surprised no one else has run into this. We use GG on RPi with a mobile cell dongle. |
I am still trying to understand how to profile Greengrass. I am certain the large data xfer is something going on in Greengrass. I have removed LogManager and also LocalDebugConsole. This leaves CLI, Diskspooler, Nucleus, clientdevices.Auth, clientdevices.IPDetector. Would any of the latter result in >40GB daily usage? |
IP detector will update the IP address whenever it changes, this can happen frequently on mobile connections. Check the greengrass log file to see what is going on; any update is logged. Use wireshark to see how many data is transferring over port 8883, 8443, and 443. These are the ports used by Greengrass. MQTT has a keepalive packet which is sent every 30 seconds, this is configurable in the Nucleus configurations. |
Feature Description
data usage
Use Case
understand mobile carrier data charges
Proposed Solution
unknown
Other
[Add detailed explanation, stacktraces, related issues, links for us to have context, etc]
(https://repost.aws/questions/QUf5la_hFMQsi2EwHuzckWNA/greengrass-carrier-data-charges)
I have seen several monitoring tools related to monitoring traffic between greengrass and AWS but none yet that really do the job of helping me understand data usage?
The text was updated successfully, but these errors were encountered: