ccsd / ledbelly Goto Github PK

LED creates an additional field called event_time_local in comparison to event_time which is in UTC. I would like to force all timestamp values to be local.

this
Time.parse(body['created_at']).utc.strftime(TIME_FORMAT).to_s
becomes
Time.parse(body['created_at']).utc.localtime.strftime(TIME_FORMAT).to_s

This would be similar to how I'm converting all timestamps to local timezone for our Canvas Data using Embulk. This saves on converting timestamps in SQL queries.

Since this affects all current users, I'm opening this up for discussion.

https://community.canvaslms.com/docs/DOC-15774-payload-example-usercreated
https://community.canvaslms.com/docs/DOC-15775-payload-example-userupdated

On Wednesday October 9, these 2 events will have the user_login and user_sis_id added to the body of the event message, these 2 fields already exist in the meta data.

Keeping with other duplicate field names between meta and body, I'll be releasing an update that adds the _meta suffix to the field names in the meta collection.
https://github.com/ccsd/ledbelly/blob/master/src/events/canvas_raw.rb#L31 and 32

The field values sent with meta data here, are the actor (user making the change), while the body values are that of the affected user.

I plan to release:
updates to the canvas raw parser
updates to the canvas raw schema
a way to easily update your database to reflect the changes.

These events will be deprecated per Release Notes...
I see no reason to clean this up before the release, and will deprecate the schema/parser after the release date.

https://community.canvaslms.com/docs/DOC-18049-canvas-release-notes-2019-12-21#jive_content_id_Live_Events

Group Events Deprecations
Events in the following groups have been deprecated and will be removed on 2020-02-18:

Quizzes Next Quiz
Quizzes.item
Quizzes.quiz Clone Job
Quizzes.quiz
Quizzes.quiz Session
Quizzes.qti Import
Quizzes-lti.grade

https://community.canvaslms.com/docs/DOC-15769-payload-example-assetaccessed

There's an issue with the DB being disconnected after the timeout, if the stream is delayed or inactive long enough for the DB timeout to expire. Increasing the timeout can help if you identify the length of the idle window. I will be working on a fix to reestablish a connection if the connection has timed out before attempting to insert a row.