-
Notifications
You must be signed in to change notification settings - Fork 37
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
Status sharing from SMP to Galaxy Uptime monitor #73
Comments
@clancger Thanks for the input, even though I think presenting this information as |
@phax Thanks, Let me check back with Galaxy |
so, here's the feedback from Hans.. |
Example output from Oxalis:
|
Here's some initial output - I think it is sufficient and does not contain sensitive information: {
"status.datetime": "2018-06-01T18:28:38.259Z",
"version.smp": "5.0.6-SNAPSHOT",
"version.java": "1.8.0_152",
"global.debug": true,
"global.production": false,
"smp.backend": "sql",
"smp.mode": "test",
"smp.resttype": "bdxr",
"smp.identifiertype": "bdxr",
"smp.id": "TEST-SMP-ID1",
"smp.writable-rest-api.enabled": true,
"smp.sml.enabled": false,
"smp.sml.needed": true,
"smp.sml.url": "https://acc.edelivery.tech.ec.europa.eu/edelivery-sml/manageparticipantidentifier",
"smp.pd.enabled": true,
"smp.pd.auto-update": true,
"smp.pd.hostname": "https://directory.peppol.eu",
"smp.certificate.configuration-valid": true,
"smp.certificate.issuer": "CN=PEPPOL SERVICE METADATA PUBLISHER TEST CA,OU=FOR TEST PURPOSES ONLY,O=NATIONAL IT AND TELECOM AGENCY,C=DK",
"smp.certificate.subject": "CN=SMP_2000000309,O=Bundesrechenzentrum GmbH,C=AT",
"smp.certificate.expired": false
} |
And here are the docs: https://github.com/phax/peppol-smp-server/wiki/Status-API |
According to the Galaxy team,
"Typically a AP page looks like this: https://atworklogin.com:8443/oxalis/status
and we parse the line, "certificate.expired: false", if it is anything else than “false” an alert is created
Is it possible to implment such a status output message in a future release?
The text was updated successfully, but these errors were encountered: