89ce4e66d7
why:
- Impact has requested some additional fields to help them enhance their
analytics offerings, as well as moving global ids to local ids to make
querying on their end much easier.
fixes INTEROP-8597
flag=lti_log_launches
flag=lti_log_launches_site_admin
test-plan:
- This plan is similar to the initial testing for the LTI Logging
commit.
- First, enable the lti_log_launches flag for your root account and the
lti_log_launches_site_admin flag.
- set up a small local server that can accept POST requests
(You can this one-liner:
ruby -e 'require "sinatra"; post("/") { puts "===", request.body.read }'
)
* configure PandataEvents in config/dynamic_settings.yml:
```yml
enabled_for_canvas: true
url: '<your server url>'
```
- restart your docker containers
- test the connection with:
`PandataEvents.send_event(:test, {foo: 'bar'})`
- your server should receive a message that includes the foo:bar payload
and some other metadata
- launch an LTI tool from the course sidebar
- your server should receive a message that includes the course, user,
tool, and account *local* ids. You should also see a root_account_uuid
and shard id.
- validate that when launching from an account placement or from a group
placement you also get the same data. Note that the
account_id will likely be the local id of your root account,
unless you put the course and thus it's group in a subaccount.
Change-Id: Ie4a8d6d0f7a410bb0556f4d090da44ca57102e29
Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/346667
Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
Reviewed-by: Xander Moffatt <xmoffatt@instructure.com>
QA-Review: Xander Moffatt <xmoffatt@instructure.com>
Product-Review: Ryan Hawkins <ryan.hawkins@instructure.com>
|
||
|---|---|---|
| .. | ||
| checkpoints | ||
| course_pacing | ||
| inbox | ||
| k5 | ||
| lti | ||
| application_service.rb | ||
| video_caption_service.rb | ||