Reviewing active usage
The Active Usage dashboard shows how much time people actively spend in Koodisi Studio, who they are, and what they build and test. In Studio it is labelled Active Time. Use it to see adoption across your organization, find your most and least active developers, and understand where people spend their time.
Before you begin
- You must be an organization administrator or the organization owner. For other members, the Active Time item does not appear, and opening the page address directly returns you to Settings.
- The data comes from a usage-analytics service that records activity in Studio. If the page shows an error banner instead of numbers, see When it does not work.
Open the dashboard
- In Studio, open Settings.
- Select Organization > Active Time.
The dashboard opens as its own full page titled Active Time, with a breadcrumb back to User Management. Select the back arrow or User Management to return to Settings.
Choose the range and idle rule
Two controls at the top apply to every number on both tabs.
| Control | What it does |
|---|---|
| Time range | The period to report on. The default is the last week. Pick a preset or set a custom range; the range can start no more than 90 days ago. |
| Count idle after | Choose 5 minutes or 15 minutes. A gap between actions shorter than this still counts as active. A longer gap counts as idle instead. |
The idle rule changes the Active and Idle figures. Changing it does not change session, user or event counts.
What counts as active time
The page footer explains how time is measured:
- Time between actions counts as active up to the idle limit you chose. A longer gap counts as idle.
- If a gap crosses a login or logout boundary, it counts as Away and is counted as neither active nor idle.
- Activity is reconstructed from click, input and page-visit events.
- The per-weekday average divides by working days only, so a team that never logs in on weekends is not reported as less active than it really is.
Active time tab
The Active time tab is the default.
Summary cards
| Card | Meaning |
|---|---|
| Active time | Total active time across all users in the range. Under it, the same total using the other idle rule, so you can compare 5 minutes and 15 minutes side by side. |
| Active users | Number of users with activity in the range. |
| Active sessions | Number of sessions with activity in the range. |
| Avg per user | Average active time per user. Under it, the average per weekday. |
Usage levels
A table of Time spent bands, with the number of Users in each band and each band's Share of active time.
Activity by hour of day
A bar chart with one bar for each hour from 00:00 to 23:00. Hover over a bar to see the hour, its number of interactions, and its number of users.
Time by platform area
Horizontal bars showing where people spent their active time, based on the screen each person had open most recently, with the active time and number of developers for each area. Areas with very little time are drawn lighter.
Usage by user
A table with one row per user, sorted by Active time, highest first. Use Search user... to filter by user name. Select a column header to sort by it.
| Column | Meaning |
|---|---|
| User | The user. Activity that cannot be tied to a person shows as "not identified". |
| Active | Active time in the range. |
| Idle | Idle time in the range. |
| Away | Time between logging out and logging back in. |
| Sessions | Number of sessions. |
| Engagement % | How focused someone was while using the platform. |
| Active days | Number of days with activity. |
Usage by day
A table with one row per day. Weekend days carry a weekend tag. Columns are Day, Active, Idle, Away, Engagement % and Active users.
Both tables show 10 rows per page, and you can change that to 20, 50 or 100. Values with no data show a dash.
Publishing & Testing tab
The Publishing & Testing tab shows what developers build and test. It has its own Developer filter. Choose All developers or one person; the list is built from the users on the Active time tab. The filter affects only this tab.
Publishing
Counts of workflows at each stage: Created, Checked, Published and Deployed. When available, a line below states what percentage of published workflows were eventually deployed. Deploys by environment shows workflows and deploys for each deployment target, with "not set" where no target was recorded.
Events
Bars showing how often each of these actions happened, with the number of developers who did them:
- Applications created
- Workflows created
- Workflows validated
- Workflows published
- Workflows deployed
- Tests executed
- Deploy profiles created
- Git activity
- Data objects created
- Schemas imported
- Traces viewed
- Metrics viewed
- Docs opened
Testing
Results of tests run on the Test API page, based on the response each call got back.
- Summary figures: Calls, OK %, Server errors and Slow call time.
- By method and type: a table with Method, Type, Calls, OK, 5xx, 4xx, Slow calls and OK %.
- Erroring test cases: a table with Test case, Calls, 5xx, 4xx and Status codes.
How you know it worked
The summary cards show figures for the chosen range. If nothing has been recorded, each section shows an empty message instead:
| Where | Message |
|---|---|
| Time by platform area | No screen-navigation events in this range |
| Usage by user, Usage by day | No active-usage events in this range |
| Usage by user, with a search | No user matches that search |
| Deploys by environment | No deploys in this range |
| Events | No matching events in this range |
| By method and type | No API test calls in this range |
| Erroring test cases | No errors in this range |
When it does not work
- Could not reach the metrics service. The analytics service did not respond. The banner shows the status it returned. Try again later or contact your administrator.
- This environment is serving the wrong OpenReplay project. The service returned data for a different project than this environment expects. The numbers on the page belong to the wrong project and should not be relied on. This is a service configuration issue, not something you can change on the page.