Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moskito-control-probe #126

Open
dvayanu opened this issue Jul 2, 2020 · 0 comments
Open

moskito-control-probe #126

dvayanu opened this issue Jul 2, 2020 · 0 comments
Assignees

Comments

@dvayanu
Copy link
Member

dvayanu commented Jul 2, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants