3ca565624f
We have seen intermittent cases where a couple of devices would be bootstrapped, then about 7 seconds later four more devices. After some investigation we found that on every fresh cloud deploy the web job would go through two starts -- we suspect this is as it goes through the staging, warmup and swap to production. To avoid letting this happen we will watch the location of the shutdown file that is created when shutdown is scheduled. If we see that before we enter the initialization method then we will skip initialization since it will likely be aborted mid-process. In Debugging we have sometimes seen cases where initialization is started, then the shutdown signal is immediatly received. However, in these cases initialization has been able to complete successfully. It may not be a perfect solution, but for now I think it's pretty solid. |
||
|---|---|---|
| .nuget | ||
| Common | ||
| DeviceAdministration | ||
| EventProcessor/EventProcessor.WorkerRole | ||
| Simulator/Simulator.WorkerRole | ||
| .gitattributes | ||
| .gitignore | ||
| AppRolesForManifest.txt | ||
| Common_Props.proj | ||
| README.md | ||
| RemoteMonitoring.sln | ||
| THIRDPARTYNOTICE (Azure IoT Suite Monitoring Solutions).txt | ||
| build.cmd | ||
| license.txt | ||
README.md
#Microsoft Azure IoT Suite ##Remote Monitoring preconfgured solution
##Contents of this repository
Web folder:
- ASP.NET MVC 5 website containing user dashboard and device portal to manage IoT devices (add, remove, view, etc)
Infrastructure folder:
- APIs and application logic to support telemetry and device operations
Simulator folder:
- Simulator (Azure Web Job) that simulates one or more devices that send data to the IoT Hub for testing and troubleshooting
EventProcessor folder:
- Azure Worker Role that hosts an Event Hub EventProcessorHost instance to handle the event data from the devices forwarding event data to other back-end services or to the remote monitoring site
Visual Studio solution:
- RemoteMonitoring: contains both the Dashboard web app, the EventProcessor worker role, and the Simulator worker role.