Azure IoT Java solution for Remote Monitoring
Перейти к файлу
sushilraje 68fd8f069d
Update run.cmd to reflect key-vault changes
2019-06-05 14:14:50 -07:00
.github
asa-manager Docs changes for keyvault 2019-04-04 15:47:44 -07:00
auth Docs changes for keyvault 2019-04-04 15:47:44 -07:00
config Docs changes for keyvault 2019-04-04 15:47:44 -07:00
device-simulation Update run.cmd to reflect key-vault changes 2019-06-05 14:14:50 -07:00
device-telemetry Docs changes for keyvault 2019-04-04 15:47:44 -07:00
docs Local deployment instructions update (#136) 2019-04-30 11:07:04 -07:00
iothub-manager Docs changes for keyvault 2019-04-04 15:47:44 -07:00
project
scripts Delete unneeded file (#135) 2019-04-15 12:00:00 -07:00
storage-adapter Docs changes for keyvault 2019-04-04 15:47:44 -07:00
.gitattributes
.gitignore
LICENSE
README.md
build.sbt

README.md

Build Issues Gitter

Remote Monitoring Microservices

Overview

Deploy to Azure

There is a .NET version of this repo available here.

Remote monitoring helps you get better visibility into your devices, assets, and sensors wherever they happen to be located. You can collect and analyze real-time device data using a remote monitoring solution that triggers automatic alerts and actions — from remote diagnostics to maintenance requests. You can also command and control your devices.

Azure IoT Hub is a key building block of the remote monitoring solution. IoT Hub is a fully managed service that enables reliable and secure bidirectional communications between millions of IoT devices and a solution back end.

Check out the Interactive Demo for a detailed overview of features and use cases.

To get started you can follow along with the Getting Started for a command line deployment. You can also deploy using the web interface at https://www.azureiotsolutions.com.

Documentation

See more documentation here.

Getting Started

Deploy a solution

There are two ways to deploy a solution:

  1. Deploy using the web interface using the instructions here.
  2. Deploy using the command line.
  3. Deploy locally using the instructions here.

Common Scenarios

Create additional simulated devices

Once you have a solution up and running, you can create additional simluated devices. You can then stop the default simulated devices by calling the simulation endpoint with the instructions here.

Connect a physical device!

By default, the solution once spun up uses simulated devices. You can start adding your own devices with the instructions here.

Customize the Web UI

You can find information about customizing the remote monitoring solution here.

Architecture Overview

Learn more about the Remote Monitoring architecture, including the use of microservices and Docker containers.

Components

How-to and Troubleshooting Resources

Feedback

  • If you have feedback, feature requests, or find a problem, you can create a new issue in the GitHub Issues
  • We have a User Voice channel to receive suggestions for features and future supported scenarios.

Contributing

Refer to our contribution guidelines. We love PRs!

License

Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT License.