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

🐛 [BUG]: Broken CanarieAPI monitoring configurations #429

Open
fmigneault opened this issue Mar 5, 2024 · 1 comment
Open

🐛 [BUG]: Broken CanarieAPI monitoring configurations #429

fmigneault opened this issue Mar 5, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@fmigneault
Copy link
Collaborator

fmigneault commented Mar 5, 2024

Summary

The CanarieAPI template configurations seem to be invalid according to what CanarieAPI looks for in logs.

Details

Configurations define for example

    "monitoring": {
        "Weaver": {
            'request': {
                'url': 'http://weaver:4001/'
            },
            'response': {
                'text': '\{.*"message":.*"Weaver Information".*\}'
            }
        }
    }

The 'http://weaver:4001/' URL seems to assume a docker-compose link connection between canarie-api (ie proxy) and the relevant services. However, looking at stats of relevant services (eg: https://hirondelle.crim.ca/canarie/Weaver/service/stats), invocations are all marked as 0 and Never accessed.

The cause might be related to how monitoring is inspected in logs. If CanarieAPI looks for the PUBLIC FQDN endpoint, (eg: https://hirondelle.crim.ca/weaver/ or https://hirondelle.crim.ca/twitcher/ows/proxy/weaver/, then there would never be a match with 'http://weaver:4001/'.

NOTE
Not 100% sure above is the cause. Needs further investigation.
Using optional-components/canarie-api-full-monitoring (which is active on Hirondelle), the full PUBLIC FQDN should be monitored as well...

To Reproduce

Steps to reproduce the behavior:

  1. Spin up an instance with any service registered under CanarieAPI.
  2. Call the service to generate logs what would be expected to be collected by the monitoring.
  3. Look up the specific stats location of CanarieAPI for the targeted service.

Environment

Information Value
Server/Platform URL any
Version Tag/Commit latest
Related issues/PR
Related components CanarieAPI
Custom configuration

Concerned Organizations

@fmigneault fmigneault added the bug Something isn't working label Mar 5, 2024
@mishaschwartz
Copy link
Collaborator

May be related: In #428 @fmigneault noticed a few places where the TWITCHER_PROTECTED_PATH was not included in URLs used by canarie-api:

'tryme': 'https://${BIRDHOUSE_FQDN_PUBLIC}/flyingpigeon/wps?service=WPS&version=1.0.0&request=GetCapabilities',

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants