Skip to content

moskito-control-probe #126

Description

@dvayanu

To provide easier way to monitor webpages or other components from different locations create a new subproject moskito-control-probe. (https://github.com/anotheria/moskito-control-probe)
This project should include a headless engine for requests and an api.
The moskito control project should receive a new connector type 'PROBE' which collects all components and their data from a probe and integrate it with a prefix.
Example: define PROBE New York with prefix NY and Los Angeles with prefix LA.
If both probes contain for example probing for same webpage, say Landing, the moskito control which includes both probes then contain component NY:Landing from NY Probe and LA:Landing from LA Probe.
Probe exposes its components via REST API which the moskito control probe connector consumers.
Probe can run as spring boot runnable with exposed API or something similar.

To make the deployment easier the probe should be packaged as docker container, the config should be added via parameter: docker run ..../moskito-control-probe:version -Dconfig=path-to-json-config

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions