WorkVie AI

AI Observability

Track WorkVie AI requests, token usage, and adoption so Alex can govern spend and prove ROI after rolling out blast-radius and CMDB intelligence to the IT team.

Real-world scenario

Alex Kim · VP of IT at Bluewave Labs

After enabling WorkVie AI for the prod-api-01 maintenance push, Alex reviews observability to see whether Platform leads adopted blast-radius queries and if token usage fits the quarterly budget.

Before you begin

  • Org admin access
  • WorkVie AI enabled and in use for at least a few days

Overview

AI Observability shows how your organization actually uses WorkVie AI, not just that it is turned on. Request counts, token breakdowns, and top surfaces help you balance enablement with cost control and spot training gaps before an audit or executive review.

Metrics available

  • Total AI requests. Volume over selectable time ranges
  • Token usage by feature. Chat, sentiment, CMDB advisory, and related capabilities
  • Top users and surfaces. Who drives consumption and from which modules
  • Errors and latency. Signals when users hit failures or slow responses

Review usage

  1. 1

    Open AI Observability

    Go to My Organization → AI Observability, or follow the link from AI Intelligence. You need org admin access.

  2. 2

    Review request volume and trends

    See total AI requests over time, spikes often follow major incidents, audit prep, or new feature rollouts.

  3. 3

    Inspect token usage by feature

    Break down consumption by chat, CMDB advisory, sentiment, and other AI surfaces to find what drives cost.

  4. 4

    Identify top users and modules

    Understand who uses WorkVie AI most and from which product areas. Useful for training and policy conversations.

  5. 5

    Adjust settings or capacity

    Use trends to tune AI settings, set internal guidelines, or plan license capacity with your WorkVerge account team.

Governance tips

Bluewave Labs: monthly AI review

  • Question: Did blast-radius usage spike before scheduled maintenance?
  • Benchmark: ~120 chat requests / week for 200-person org
  • Action if over budget: Narrow feature toggles in AI Settings
  • Action if under-adopted: Share workspace prompts with team leads

Pair with executive reports

Export or mirror key metrics on a shared dashboard via Reports when finance asks for AI line-item justification.

Related articles