Skip to content
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.

Releases: Azure/azure-iot-pcs-remote-monitoring-java

3.0.0

17 Apr 18:24
Compare
Choose a tag to compare

April Updates

The latest update of Azure IoT Remote Monitoring (3.0.0) simplifies the way configuration is done throughout the solution. Previous iterations made heavy use of environment envariables. For various systems / IDEs / etc environment variables are set up in different ways making understanding and maintaining Remote Monitoring more difficult. Adding a new variable into the system required plumbing into numerous parts of the system such as the CLI / kubernetes configuration / docker compose files / scripts and more. The latest Remote Monitoring will provision a Key Vault resource to simplify this process.

New Resources

Provide Feedback and Ask Questions

We’d love your feedback! We have a User Voice channel to receive suggestions for features and future supported scenarios. We encourage you to browse what others are suggesting, vote for your favorites, and even enter suggestions of your own.

If you run into problems with the solution please open issues on our GitHub repositories (.NET and Java)
Please review our public FAQ for answers to the most common questions

2.2.0

21 Mar 23:35
Compare
Choose a tag to compare

February Updates

We are excited to announce the latest update of Azure IoT Remote Monitoring Version 2.2.0, a solution accelerator that is fully operational right out of the box. Updated features and improvements for February can be found below:

  • Improvements:
    • UI is now using fluent controls which is a common controls library for all of Azure IOT.
    • Accessibility is improved in UI and all the errors in "Accessibility Insights" tool are fixed.
    • Device Simulation's Status service bug is fixed
    • Diagnostics service's environment variable bug is fixed
    • More miscellaneous bug fixes

Provide Feedback and Ask Questions

We’d love your feedback! We have a User Voice channel to receive suggestions for features and future supported scenarios. We encourage you to browse what others are suggesting, vote for your favorites, and even enter suggestions of your own.

If you run into problems with the solution please open issues on our GitHub repositories (.NET and Java)
Please review our public FAQ for answers to the most common questions

2.1.3

28 Jan 18:37
Compare
Choose a tag to compare

January Updates

We are excited to announce the latest update of Azure IoT Remote Monitoring Version 2.1.3, a solution accelerator that is fully operational right out of the box. Updated features and improvements for January can be found below:

  • Improvements:
    • Device Simulation: Downgraded to 1.0.3 due to device restart issue in latest Device Simulation.

    • Bug Fixes: Some minor bug fixes in webUI and services.

Provide Feedback and Ask Questions

We’d love your feedback! We have a User Voice channel to receive suggestions for features and future supported scenarios. We encourage you to browse what others are suggesting, vote for your favorites, and even enter suggestions of your own.

If you run into problems with the solution please open issues on our GitHub repositories (.NET and Java)
Please review our public FAQ for answers to the most common questions

December Updates

03 Dec 18:16
Compare
Choose a tag to compare

December Updates

We are excited to announce the latest update of Azure IoT Remote Monitoring, a solution accelerator that is fully operational right out of the box. Updated features and improvements for December can be found below:

  • New Features:

    • Automatic Device Management: Azure IoT automatic device management helps facilitate bulk device management by allowing operators to target a set of devices, define the changes to be applied, and then choreograph the changes as devices become available. It also automatically handles reporting and conflict resolution, which greatly reduces the possibility of human error. We have now integrated automatic device management into Remote Monitoring so that operators can create, deploy, and manage automatic device configurations right from the web UI. For a walkthrough example of how to use this, you can follow our tutorial on implementing a firmware update for an MX Chip.
  • Improvements

    • Role Based Access Control (RBAC) has been recently updated in this latest release to lock down users who can view and interact with the solution. This means that the user who deployed the solution is the only person who can view it immediately after it has been created. To grant others access to view the application as either a Read Only, Admin, or a Custom role, see the following directions below on add or remove users. Learn more here about the updates made to RBAC and how to grant users access.

Provide Feedback and Ask Questions

We’d love your feedback! We have a User Voice channel to receive suggestions for features and future supported scenarios. We encourage you to browse what others are suggesting, vote for your favorites, and even enter suggestions of your own.

If you run into problems with the solution please open issues on our GitHub repositories (.NET and Java)
Please review our public FAQ for answers to the most common questions

2.0.0

26 Nov 19:10
Compare
Choose a tag to compare

November Updates

We are excited to announce the latest update of Azure IoT Remote Monitoring, a solution accelerator that is fully operational right out of the box. Updated features and improvements for November can be found below:

  • New Features:
    • Edge: Real-time data analytics & insights drive business value in IoT solutions, but not all customer scenarios can rely on cloud processing. Azure IoT Edge solves these challenges by delivering cloud intelligence locally on IoT devices. Azure IoT Edge is now seamlessly integrated with the Azure IoT Remote Monitoring solution accelerator. Customers can leverage this feature to reduce bandwidth costs by processing data locally or achieving near real time actions by using AI at the edge.
    • Email Actions: Adding an email action to a rule helps to ensure that you will never miss an alert again. Actions can be added to existing rules defined in your solution, or while creating a new rule. This ability to acting on device alerts within Azure IoT Remote Monitoring is is possible through the integration of Azure Logic Apps, which has a rich set of extension points available for developers. This allows customization into other scenarios such as sending text messages, triggering business processes to services such as Dynamics, or calling a webservice API endpoint. You can learn more about how to customize your actions in Azure IoT Remote Monitoring here

Provide Feedback and Ask Questions

We’d love your feedback! We have a User Voice channel to receive suggestions for features and future supported scenarios. We encourage you to browse what others are suggesting, vote for your favorites, and even enter suggestions of your own.

If you run into problems with the solution please open issues on our GitHub repositories (.NET and Java)
Please review our public FAQ for answers to the most common questions

1.0.2

14 Nov 16:38
Compare
Choose a tag to compare

September Updates

We are excited to announce the latest update of Azure IoT Remote Monitoring, a solution accelerator that is fully operational right out of the box. Updated features and improvements for September can be found below:

  • Improvements:

    • Walkthroughs have been added to help customize the User Interface
      • Add a new page
      • Add a new service
      • Add a new grid
      • Add a new flyout
  • New Features:

    • Azure Time Series Insights: New Remote Monitoring deployments will now include Time Series Insights. All messages data will be stored in Time Series Insights, while alarms, rules, configuration settings and all cold storage will continue to be stored in Cosmos DB. Users will also be able to access the Time Series Insights explorer through the Remote Monitoring web UI, allowing them to gain deeper insights into sensor data by spotting trends, anomalies, and correlations across real-time and historical data in all locations.This feature will be available globally except for China, which will keep using Cosmos DB.
  • Issues Fixed:

    • Fixed the Jobs Execution Failure: Executing a firmware update in Remote Monitoring is now reflected in both the UI and devicetwin. Issue
    • The following WebUI fixes have been made:
      • Treat text and number correctly in device jobs issue
      • WebUI crashes when the twin has nested tags issue
      • Update device statistics header when filters are applied issue
      • Start / Stop sensor flow control rendering in IE issue
      • Deleting all rules then adding a new rule threw an error issue

Provide Feedback and Ask Questions

We’d love your feedback! We have a User Voice channel to receive suggestions for features and future supported scenarios. We encourage you to browse what others are suggesting, vote for your favorites, and even enter suggestions of your own.

If you run into problems with the solution please open issues on our GitHub repositories (.NET and Java)
Please review our public FAQ for answers to the most common questions

2.1.2-rc.1

11 Dec 23:01
Compare
Choose a tag to compare
Docs improvements (#61)

* Update README.md

* Update LOCAL_DEPLOYMENT.md

* Update LOCAL_DEPLOYMENT.md

* Update LOCAL_DEPLOYMENT.md

* Update LOCAL_DEPLOYMENT.md

* Update LOCAL_DEPLOYMENT.md

2.1.1-rc.1

11 Dec 19:35
Compare
Choose a tag to compare
Docs improvements (#61)

* Update README.md

* Update LOCAL_DEPLOYMENT.md

* Update LOCAL_DEPLOYMENT.md

* Update LOCAL_DEPLOYMENT.md

* Update LOCAL_DEPLOYMENT.md

* Update LOCAL_DEPLOYMENT.md

1.0.1

16 Aug 21:00
Compare
Choose a tag to compare

What’s new in Remote Monitoring

We are excited to announce the latest update of Azure IoT Remote Monitoring, a solution accelerator that is fully operational right out of the box. Updated features and improvements for August can be found below:

  • Improvements:

    • Added a new repo for integration tests for end to end scenarios.
    • Cache changes to remove remote dependencies in the configuration.
    • Security Fixes to align with Security Development Lifecycle.
    • Builds migrated to VSTS instead of Travis.
  • New Features:

    • Piloting in-product analytics: In an effort to keep improving the Remote Monitoring solution accelerator, we are now piloting in-product analytics to better understand how the product is being use. No personal information will be tracked or collected. If you would like to opt out of sending us your telemetry, please click the settings gear at the top of the Web UI and toggle the option off.
    • Roles based access: "Read Only" and "Admin" roles allow users different levels of access to modify rules, device groups, and alerts to ensure data security. By restricting access to key features to a limited set of Admin users, someone attempting to modify important data can only do so if it is deemed necessary for their role.
    • Delete Rules: Rules can now be deleted from the rules page on the Web UI. Simply click the checkbox next to the rule and click delete at the top. Alert history for this rule will still be saved for reporting purposes.

Provide Feedback and Ask Questions

We’d love your feedback! We have a User Voice channel to receive suggestions for features and future supported scenarios. We encourage you to browse what others are suggesting, vote for your favorites, and even enter suggestions of your own.

If you run into problems with the solution please open issues on our GitHub repositories (.NET and Java)
Please review our public FAQ for answers to the most common questions

1.0.0

05 May 00:57
Compare
Choose a tag to compare

Azure IoT Remote Monitoring solution goes out of Preview

Azure IoT solutions accelerators bring the next wave of innovation

In October, we announced a major update to Azure IoT Remote Monitoring, our focus on operator scenarios built on a flexible open source architecture represented an evolution in our solutions. Remote Monitoring is aimed at accelerating our customers to production deployments, with lower cost, a redesigned UI, enhanced operator scenarios, and flexibility for customizations.

In six months we have seen incredible momentum. Customers are moving faster through their initial phases of development, and in a matter of weeks onto real-life scenarios. More customers and partners than ever before are leveraging Remote Monitoring to deploy production solutions.

Today, we are excited to announce the next stage in our evolution of customizable solutions from Azure IoT Suite Preconfigured Solutions to Azure IoT Solution Accelerators. Future investments will be in both horizontal and industry specific scenarios that customers and partners can customize and take to production faster.

What’s new in Remote Monitoring

We are excited to announce the latest update of Azure IoT Remote Monitoring, a solution accelerator that is fully operational right out of the box. New features include:

  • Enhanced UI: Operator experiences are even smoother with production-ready controls, and improvements in code clarity allow any React developer to customize with ease.
  • Enhanced operator scenarios:
    • Advanced rules and streaming powered by Azure Stream Analytics engine.
    • Live maintenance mode to track your devices telemetry while doing maintenance.
    • Richer out of the box demo experience
    • Easier device connectivity: see your device details light up in the platform automatically, no need to customize the UI.
    • Better maps: our device tracking is now powered by Azure Maps, the latest technology to provide geospatial context to data.
    • Richer integration options: we have invested in third party integration. We have new tutorials that showcase integration with services such as Power BI, Azure Time Series Insights, Azure Data Lake, and Azure Logic Apps.
    • New SIM Integration, powered by Telefonica IoT. Customers using Telefonica SIM data will be able to seamlessly manage their devices using the Remote Monitoring solution.

Why this release is important to customers and partners

With Remote Monitoring being out of preview, your customers and partners will get the peace of mind that our architecture will evolve in a way that they will be able to consume with minimal breaking changes. While the project is open source, we are committing to provide an experience where both customers and partners can both contribute back and update their projects with our upcoming releases.

Get Started

Explore the solution code

Both versions of the solution are open source and ready for full customization starting today. Please start exploring based on your preferences:

Documentation and resources

We listened to your feedback around providing better guidance to use the solution: This release has more than 10 new documents that will help you drive more scenarios with our solutions. You can check out our docs here:

Provide Feedback and Ask Questions

  • We’d love your feedback! We have a User Voice channel to receive suggestions for features and future supported scenarios. We encourage you to browse what others are suggesting, vote for your favorites, and even enter suggestions of your own.
  • If you run into problems with the solution please open issues on our GitHub repositories (.NET and Java)
  • Please review our public FAQ for answers to the most common questions