Open ccsmart opened 6 years ago
@ccsmart we should perhaps look at Nagios https://www.nagios.com/solutions/url-monitoring/ , https://www.nagios.com/solutions/website-monitoring/
This is not about monitoring in that scope. For this IT departments have their solutions. This request is about a tool to allow simple verification of the status of an installation.
@ccsmart ok you mean like a service to check if the package got installed. For gawati-data it is there:
/gwd/about
e.g. :
$ curl http://data.local/gwd/about
package=gawati-data;version=1.12;date=2018-03-08
will add something similar for other services. Perhaps the output should be in a predictable format. plain text like the above fine ?
Exactly. Semicolon as separator seems good. No collissions expected.
A testclient for that is here: https://github.com/gawati/setup-scripts/blob/dev/gawati/installer/gawatiportal/scripts/01/gawaticheck
@ccsmart done for gawati-portal-server, gawati-client-server, gawati-data, gawati-client-data. For portal-ui it cannot be tested this way. Its a pure client rendered implementation i.e. the page is rendered by executing javascript which curl cannot do.
should be ok to just place a file containing that data, maybe generated during build by Jenkins... ?
for gawat-client-server fails for me:
[root@msicentos gawati-portal-ui]# curl -k https://data.dev.gawati.org/gwc/about <!DOCTYPE html>
Error: Not Found at /home/gawatidevclientsrv/portal/app.js:58:13 at Layer.handle [as handle_request] (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:317:13) at /home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:335:12) at next (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:275:10) at /home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:635:15 at next (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:260:14) at Function.handle (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:174:3) at router (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:47:12) at Layer.handle [as handle_request] (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:317:13) at /home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:335:12) at next (/home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:275:10) at /home/gawatidevclientsrv/portal/node_modules/express/lib/router/index.js:635:15
@ccsmart can you verify if you have this commit : https://github.com/gawati/gawati-client-server/commit/6870cc3e9140d7df2b5d4f887943ff7f5d777619
looks like it, yes. as amendment, get the same result with curl -k http://localhost:9102/gwc/about
curl http://localhost:9102/gwc/about issue solved. was due to missing files in deployment.
last one missing for completion is gawati-user-profiles
Gawati consist of several services on several base URLs. This is a request for a tool that allows to define base URLs for each of the services of a Gawati instance. The tools primary task is to verify availability of each service. The tool might for each service: