Monitoring is an important part of maintaining the reliability, availability, and performance of AWS IoT and your AWS solutions.
We strongly encourage you to collect monitoring data from all parts of your AWS solution to make it easier to debug a multi-point failure, if one occurs. Start by creating a monitoring plan that answers the following questions. If you're not sure how to answer these, you can still continue to enable logging and establish your performance baselines.
What are your monitoring goals?
Which resources will you monitor?
How often will you monitor these resources?
Which monitoring tools will you use?
Who will perform the monitoring tasks?
Who should be notified when something goes wrong?
Your next step is to enable logging and establish a baseline of normal AWS IoT performance in your environment by measuring performance at various times and under different load conditions. As you monitor AWS IoT, keep historical monitoring data so that you can compare it with current performance data. This will help you identify normal performance patterns and performance anomalies, and devise methods to address issues.
To establish your baseline performance for AWS IoT, you should monitor these metrics to start. You can always monitor more metrics later.
The topics in this section can help you start logging and monitoring AWS IoT.
Security best practices
Configure AWS IoT logging
Did this page help you? - Yes
Thanks for letting us know we're doing a good job!
If you've got a moment, please tell us what we did right so we can do more of it.
Did this page help you? - No
Thanks for letting us know this page needs work. We're sorry we let you down.
If you've got a moment, please tell us how we can make the documentation better.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4