-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Labels
Description
Describe the bug
In some situations, monitoring seems to incorrectly update its latest update time.
bird-house/birdhouse-deploy#284 (comment)
There also appears to be other cases were "access" logs (when monitoring paths of the services are accessed) are not updating the services and platform invocations and lastAccess values, although lastInvocationsUpdate and lastStatusUpdate do seem to udpate, indicating that the crons are properly running, but something is not updated/stored correctly. See /canarie/server/platform/stats and /canarie/node/service/stats , or any other service.
To Reproduce
- Start a birdhouse-deploy instance and wait for a minute or two.
- Go to
/canarie/node/service/statusendpoint of the instance to checklastUpdateStatus.
Expected behavior
lastUpdateStatus should update with the cron job set for every minute.
Screenshots
n/a
Environment
- OS: Linux
- Browser: any
- Instance: any
- Version:
0.7.1(not strictly, but observed with this version)