Roleplay Analytics · IIFL Sarvam

Backend: checking… Logs uploaded: —

1 Upload logs The export of app-yodagptbackend-prod-01's logs (AppServiceConsoleLogs) for the period you need: .ndjson / .json / .csv, plain, .gz or .zip.

2 Period

From / to (IST) Group by

3 Compare with

Pick a window and press Analyse.

Sessions—

Completion rate—

Never heard once—

Heard, then stopped—

Ran but not scored—

Never connected—

Completion rate

Share of sessions completed (more than 3 exchanges saved and scored), per period.

Sessions

Sessions started per period (IST).

Where sessions are lost

Share of all sessions reaching each step.

Why sessions fail

Failure categories, % of all sessions. One category per failed session.

Failure categories in detail

What each category is read from in the logs or the mic recording.

Mic warnings

First warning the app was sent in each session (the app shows only one). "Heard after" = a learner turn was committed after it.

Language

Share of sessions and completion rate per session language.

Device / browser

From the app's client_info message (user agent). "Not reported" = the mic never started, so the app never sent it.

Data: the uploaded prod backend logs of app-yodagptbackend-prod-01 and the learners' mic recordings, processed by the backend on this PC (start_backend.bat). Times are IST. The Excel has the same 70 columns as "IIFL Sarvam Roleplay Sessions 21-28 Sep"; learner, cohort, scenario, score and transcript columns fill in once the CRUD export is added to the backend.