gorums/WatchIoT

View on GitHub
README.md

Summary

Maintainability
Test Coverage
[![Stories in Ready](https://badge.waffle.io/watchiot/watchiot-web.png?label=ready&title=Ready)](https://waffle.io/watchiot/watchiot-web)
WatchIoT [![Build Status](https://travis-ci.org/watchiot/watchiot-web.svg)](https://travis-ci.org/watchiot/watchiot-web) [![Code Climate](https://codeclimate.com/github/watchiot/watchiot-web/badges/gpa.svg)](https://codeclimate.com/github/watchiot/watchiot-web) [![Test Coverage](https://codeclimate.com/github/watchiot/watchiot-web/badges/coverage.svg)](https://codeclimate.com/github/watchiot/watchiot-web/coverage) [![Inline docs](http://inch-ci.org/github/gorums/watchiot.svg?branch=master)](http://inch-ci.org/github/gorums/watchiot) 
==

**A monitor services, resources and IoT**

Multi-Platform
--

You can monitor different platforms, like the resources of your server on linux, windows or any application in the cloud and the smart devices (Internet of Thing).

Configurable
--

The power of Watch IoT is whole configurable, you can configure what server or resource you will monitor, what parameters you will receive and when the system will throw an alert for you.

Notification
--

The notifications via email and sms are in real time about what is happened with your services or resources. Feel secure, you have all under control and you can sleep relaxing we are going to stay alert for you.

Bidirectional
--

Watch IoT can request your services or you services can request Watch IoT, dependent your necessities. You can specify period of time when send the request you services or who you expect for the request.

Scripting
--

You have two way of parser the request/response. Using configured params or can create scripting to parse your values. You can take decision using the scripts about who would be notified.

Charting
--

All history data can be shown using charting and you can see how your services have worked. The charting always is a great tool for understand health of your services and resources.

Changelog
--
*20 March 2016*

All the tests were complete

*30 november 2015*

Link heruko with new domain www.watchiot.com

*4 october 2015*

Struct site defined

*1 september 2015*

Dashboard work begin

*15 august 2015*

Finished the first part of the home page

*1 june 2015*

Create watchIoT project on github, first commit