Running the System
Run mvn clean compile package on all the services
Product Name: SysCop
Problem statement: Build a non-Invasive Infrastructure Monitoring System IT Organizations have pockets of infrastructure comprising both legacy and new systems.
Problem statement in details: Monitoring such infrastructure is a challenge. This is primarily due to the invasive nature of existing infrastructure monitoring tools in the market. Such monitoring systems often require adding instrumentation code to existing code base to emit monitoring metrics. Often this is not possible due to inaccessible source code, such as external vendor systems. Also the pain and risks involved in updating, building, and redeploying a running system is too big to warrant for any such operations. Another problem to identify and accept is that software monitoring is not only about detecting failure and reporting them - what almost all existing monitoring tools do. As a result, by the time failure is detected, reported, and then some action taken, the damage is already done. So the key challenge to solve is, how can a monitoring system intelligently predict a software failure instead of reporting after a failure? SysCop is an infrastructure monitoring system that can be attached to existing running systems and start monitoring them. The monitoring system is extensible to use in legacy application as well as modern containerized application infrastructure. SysCop is technology agnostic as it uses the concept of extensible metrics gathering agents. SysCop have analytical capabilities to automatically detect and threat to the infrastructure. SysCop uses time-series data to recreate events on any point of time for analysis.
Services and their dbs:
- Registration Service-mongo
- Login (Both user and admin) Service-mySQL
- Application Registration Service-mongo
- Dashboard Service
- Monitoring Service-Influx
- Data Collector Service
- Alert Service
- Processor Service-Influx
- Agent Service-mongo
- Threshold Service-mongo/sql