Skip to main content

Usage Analysis changelog

2.7.0 (2026-07-16)

  • Release: Tests slow-test alert now compares each test's latest duration against both the bleeding-edge recent average and the previous release (previous minor semver, found across instances) and shows both deltas; sub-second tests are ignored to cut noise; ReleaseTests returns a prev_release_ms baseline. (Stress keeps its bleeding-edge p95-vs-prior comparison — the previous release has no stress data to compare against.)

2.6.1 (2026-07-16)

  • Release: Tickets — match the "Main" label case-insensitively (was looking for "MAIN", so the MAIN panel was always empty)

2.6.0 (2026-07-16)

  • Release: Added a global Environment (instance) picker to the dashboard ribbon that persists across all tabs and filters Overview and Tests to builds run on the selected instance (replaces the per-tab Tests instance input)
  • Release: Tests tab — per-row mute icon (🔔/🔕) mutes a test for the current release version; version-bound mutes are stored in a dedicated ReleaseMutes sticky-meta schema and drop the test out of the failing/unstable/needs-attention counts for that version
  • Release: Tickets tab — the tickets grid now fills the page
  • Release: Tests tab — when a test didn't run in the latest build, its last known result is carried forward (shown dimmed) and used for the failing/pass-rate counts
  • Release: Added a "not run for 7+ days" stale-test alert (Overview + a stale_days column), with a separate per-row mute independent of the failing mute; ReleaseTests now returns each test's last run date over a 14-day lookback
  • Release: Tickets tab — color-coded status/priority/resolution cells; MAIN-labelled tickets shown in their own panel; the Overview Tickets card counts only actionable tickets (not Done / Won't Fix) split into MAIN vs other
  • Release: Added a global Refresh button to the dashboard ribbon that reloads every tab
  • Release: ReleaseTests now counts the latest CI/CD run per test (like TestsDashboard) instead of every test_run — retried-then-passed tests no longer count as failing and non-CI runs are excluded, so the failing counts stop being inflated by reruns
  • Release: Tests tab — the detail grid now fills the page; per-build status cells show + (passed) / (failed) / · (skipped)
  • Release: Stress tab — replaced the last-build scatter plot with a box plot of duration by thread count (zero-padded threads_string category for numeric ordering, logarithmic ms axis); fixed charts being clipped by the fixed-height panel host

2.5.4 (2026-07-15)

  • Release: Beautified the Tests grid — per-test passing history across the last 5 builds (color-coded status cells + a passing sparkline) and a duration sparkline, sorted to surface failing/flaky/slower tests first (mirrors the Overview alerts)
  • Release: Fixed the success rate rounding up to 100% while tests were failing (now floored); the Tests card sub shows "N passed, M failing"

2.5.3 (2026-07-15)

  • Release: Overview alerts pane fills the view and groups a second level by package (category → package → test); the success rate excludes skipped and did-not-run tests (passed / passed+failed, floored)

2.5.2 (2026-07-15)

  • Release: Added a dev-only /release release-readiness dashboard (Overview + Tests + Manual + Stress + Vulnerabilities + Tickets) — reuses the Stress/Vulnerabilities tabs, adds a per-package Tests tab (unit/integration/package tests, success & duration sparklines, sticky-meta muting, raw+Jenkins drilldown), a Manual (Test Track batches) tab, and a Jira fixVersion Tickets tab, with an Overview of traffic-light status cards and computed alerts. Vulnerabilities show bleeding-edge core scans (release-channel core excluded)

  • Release: Overview alerts are a navigable tree (categories → individual tests, click to open the tab); the vulnerabilities alert compares bleeding-edge vs the previously released image (new critical/high only); the test speed-regression check uses only passed runs; every grid has a '+' to open it as a table in the workspace; the Vulnerabilities grid is sorted by category

  • Release: Fixed a "Wrong range" grid error on the Tests tab by deferring sparkline columns until the grid is laid out

  • Vulnerabilities: Added a tab showing the published VEX scan results (data.datagrok.ai/vex) — per-image severity summary with drill-down to the per-CVE report

  • Stress: Added a tab with per-build stress metrics (median duration by build split by threads, full metrics grid) and a last-build scatter plot (threads vs duration, colored by pass/fail)

  • Metrics: Fixed app registration url ('/' → '/metrics') that shadowed all Usage Analysis deep links — any /apps/usage/ URL used to land on Metrics

  • Stress: Added passthrough JS post-processing to StressTestsRaw/StressTestsSummary — project datasync of plain (post-process-free) queries loses the result dataframe client-side, which broke the CicdTests dashboard's stress views on open

  • Added the vexImages function (VEX scan results as a dataframe) — feeds the CicdTests dashboard's data-synced VEX view; core images use their bleeding-edge scan, packages/tools the latest released scan

  • Added stressSummaryDashboard/stressRawDashboard wrapper functions for the CicdTests dashboard's stress tables (project datasync of DataQuery calls is unreliable — GROK-20391)

  • Tests dashboard: Added an Unignore button next to "Mark as triaged" in the test properties panel — clears the ignored flag and its reason

  • Stress tests: Replaced the old stress dashboards/queries with StressTestsSummary (all builds — median/avg/min/max/p95 of ms by threads, pass rate as the mean per-test pass fraction), StressTestsRaw (per-build raw runs incl. error text, latest default, boxplot of ms), and StressTestsFailures (failing test×thread combos with a sample error); rewired the CI/CD tests project. Backed by the new server stress_tests table populated from the Jenkins stress job.

  • GROK-14456: Usage Analysis: Log tab improvements (added parameter details to the context panel and stack traces for errors)

  • GROK-12108: Usage Analysis: Errors tab

  • GROK-19820: Jira swagger: Removed three unused endpoints, keeping only Jira Create Issue

  • Metrics: Added Admin Metrics dashboard tab

  • TestTrack: Fixed node-expansion errors after the Test TrackTestTrack folder rename — the loader now skips -run run reports and -spec.ts files (filtered to ``) instead of parsing them as test cases, and guards against a null category node

  • GROK-16262: TestTrack: Removed the Browse > Browse tree states test case

2.5.1 (2026-05-21)

  • TestTrack: Wired Playwright suite (files/TestTrack) into grok test via the new playwrightTests opt-in; specs now authenticate via the same dev-key→token flow as the Puppeteer pass and run in CI alongside existing tests
  • Test Dashboard: Moved "Watch a jira ticket" storage from the ua_tickets Postgres schema to a JSON file in System:AppData/UsageAnalysis/manual-tickets.json; removes the package-owned schema (and its UA_tickets connection / ManualTicketFetch / ManualTicketCreation queries) so UA installs cleanly on customer envs without CREATE SCHEMA/ROLE privileges
  • Test Dashboard: Wired the JIRA-ticket verdict grids back into onFrameAttached so watched/auto-detected tickets now render as priority-bucketed grids in the dashboard accordion (previously the display path was defined but never called)
  • Test Dashboard: Removed dead code (~115 lines): unused verdictsOnTestTrack/testTrackDowngrades, commented-out unaddressedTests block, stray debugger statement, and several unused locals
  • Click Events widget: Added date range filter, section labels, highlight zones tooltip

2.5.0 (2026-03-20)

Features

  • GROK-18787: Click Tracking:
    • Added Clicks tab
    • Added tab control for Click Analysis and Specific Clicks
    • Added elements inspect
  • #3213: Introduced Projects tab
  • Improved query performance, load time, and projects tab
  • Reports: Added descending ordering by creation date in widget
  • Reports: Truncated long text in widget
  • Improved ticket loading with bulk method and background processing
  • Decreased bundle size by removing unnecessary test library usages
  • #3604: Migrated tags to roles

Bug Fixes

  • GROK-19855: Reporting app now loads reports when opened by URL with report number
  • GROK-19523: AppTreeBrowser decorator now finds the app properly
  • GROK-19504: Invalid datagrok-api imports corrected

2.4.2 (2025-09-26)

  • Test Track: Added advanced test case for visual query
  • Reports: Fixed not visible add rule button
  • TestTrack: Removed manual test that have autotest
  • GROK-18772: ManualTests Dashboard: Unable to parse string "Test Track:test" when trying to "Run" test
  • Test Track: updated and refined test cases for Projects (added Spaces)
  • Tests: Added warning about missing packages tests
  • Update Autocomplete
  • Update Formula Refreshing
  • GROK-17332: Removed unused queries
  • Table name change
  • Test Track: Line chart: Added context menu for test cases
  • GROK-18366 Usage analysis: Log: an error occurs when opening the tab
  • UsageAnalysis: Api: naming fixes

2.3.2 (2025-03-24)

  • Tests Dashboards: improvements for gathering of benchmarks

2.3.1 (2025-03-13)

  • Dependency: datagarok-api >= 1.24.0*

Features

  • Tests Dashboards: improvements and bug fixes
  • Stress tests dashboards revisited

2.3.0 (2025-02-18)

  • Dependency: datagarok-api >= 1.24.0*

Features

  • Packages: Possibility to filter packages by category
  • Functions: Possibility to filter functions by tags
  • Improvements in usage queries and bug fixes
  • Tests Dashboard

2.2.1 (2024-12-03)

  • Dependency: datagarok-api >= 1.22.0*

Features:

  • Added detector for tests tables
  • Updated test track business logic
  • Added test cases to Test Track app

2.2.0 (2024-10-24)

  • Dependency: datagarok-api >= 1.22.0*

Features:

  • Reporting: Better subscriptions handling
  • Service logs app: Application that gives possibility to see logs of different services within Datagrok infrastructure.

2.0.2 (2024-07-23)

  • Dependency: datagarok-api >= 1.20.0*

Features

  • Reporting: Bugs fixes and improvements in UX
  • Test Track:
    • Collaborative testing synchronization
    • Ability to set severity level of errors
    • Ability to associate test executions with Error reports
    • Updates Test Track according new tests registration

2.0.1 (2024-06-12)

Features

  • Reporting app

2.0.0 (2024-03-16)

  • Dependency: datagarok-api >= 1.18.0*

Features

  • Test Track released
  • GROK-14344 UA: Functions execution time
  • UA: update routing, overall improvements
  • UA: Test results for selected date in Test Track
  • UA: Compare test results in Test Track
  • GROK-14402 UA: Test Track

1.0.4 (2023-11-27)

Dependency: datagarok-api >= 1.17.3

Features

  • GROK-13271 Usage Analysis: Logs view (#2363)
  • UA: Refactor Usage tab for Packages & fixes

Bug Fixes

  • UA: Tests fixes
  • Enabled cards caching

1.0.3 (2023-11-09)

Dependency: datagarok-api >= 1.16.1

Features

  • UA: Packages installation time
  • Overall improvements

1.0.2 (2023-10-31)

Dependency: datagarok-api >= 1.16.1

Features

  • GROK-13425 UA: Ability to call query without loading from server
  • GROK-12578 UA: Tests
  • GROK-13721 Test Track (WIP)
  • UA:
    • Speedup
    • CSS tweaks
    • Better choiceInput
    • Client side cache
  • GROK-13947 UA | TM: Usage tab for packages

Bug Fixes

  • UA: Fixes GROK-13498 & GROK-13500
  • UA: Queries & widget fixes

1.0.1 (2023-07-03)

Dependency: datagarok-api >= 1.13.8

Features

  • Speedup, cleanup and styles fixes
  • GROK-13342 Resurrect test tracking system

Bug Fixes

  • Query deploy bugfix

1.0.0 (2023-05-10)

Dependency: datagarok-api >= 1.13.8

Features

  • GROK-12111 UsageAnalysis: Packages tab
  • GROK-12745 UsageAnalysis: Functions tab
  • GROK-12796 UsageAnalysis: Widget
  • GROK-12110: Usage Analysis: Overview tab
  • GROK-12109 UsageAnalysis: Events tab
  • UsageAnalysis: Cards
  • Overall fixes & improvements

Bug Fixes

  • GROK-13127 UsageAnalysis: error in widget