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

Add monitoring for Caliper events #39

Open
2 tasks
zqian opened this issue Jun 25, 2024 · 1 comment
Open
2 tasks

Add monitoring for Caliper events #39

zqian opened this issue Jun 25, 2024 · 1 comment

Comments

@zqian
Copy link
Member

zqian commented Jun 25, 2024

Currently we have experienced outage of Kaltura Caliper events. It would be good to have a monitoring routine for various Caliper feeds (Canvas, Kaltura, Lecture Capture, etc.):

  • check whether there is new events sent in last X hours ( X could vary: 4 hours during working hours, 6 hours during off time?)
  • send alert messages with the Caliper data source marked in the subject line

Sample Caliper event queries are listed in the MyLA Wiki. Need to add time frame into the query

@jonespm
Copy link
Member

jonespm commented Jun 25, 2024

This would either need a full rewrite of the existing monitoring queries to use BigQuery or just add in an additional BigQuery connection for this one check. I think it would be nicer if everything used BigQuery but don't know the effort of that.

The query that might be helpful for returning the last date could be this, then check if anything is older than X days. This for instance would pull the dates for the last 2 weeks, this might be fine to just have it at 1 week.

SELECT distinct ed_app.id, max(datetime(event_time)) as last_update FROM `udp-umich-prod.event_store.expanded` WHERE 
  event_time BETWEEN DATETIME_SUB(CURRENT_DATETIME(), INTERVAL 2 WEEK) AND CURRENT_DATETIME()
  group by ed_app.id
  order by last_update desc;

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