Chandler usage · session

Session

User: chris.scott@dext.com · Chris Scott
Started: 2026-09-16 17:15
Last activity: 2026-09-16 17:15
Questions: 1
Grouping: time_gap — inferred — consecutive questions from this user with no long gap
session_id: ba995a01-0dbb-4a67-ad2b-f6e34517f1a1

Transcript

2026-09-16 17:16 ask success $0.3739 24.9 s full detail →

I need monthly bookings by sales rep, globally, for each month January 2026 through August 2026 inclusive. Before running a large query, please tell me how the model handles this: 1. Which measure is the governed "bookings" measure, and what does it count (new MRR? ARR? contract value?) 2. Is there a dimension that splits bookings into New Business vs Existing Business, and within Existing Business into Expansion vs Attrition/Contraction? I need those three categories separately because targets are set that way. 3. Which field is the sales rep / opportunity owner, and is there a team or region dimension alongside it? 4. Which date field drives the month (close date, booking date, effective date)? Give me the field names and the definitions, not the full dataset yet.

The model defines bookings as the total value of customer contracts raised and sold in a given period, with no distinction between annual and monthly contracts. However, the excerpts do not identify a governed bookings measure or the fields needed for your requested breakdown, so I cannot accurately build the query yet. 1. **Bookings measure:** The measure’s field name is not documented. The business definition is contract value, not new MRR or ARR. 2. **Business categories:** No fields are documented for New Business versus Existing Business, or for Expansion versus Attrition/Contraction within Existing Business. Acquisition-date fields mention New Business, Winback and Reactivation, but do not provide the requested bookings categories. 3. **Sales rep and organization:** No sales rep, opportunity owner, team or region fields are documented. 4. **Monthly date:** Period analysis must use `omni_dbt__eds_calendar_day.date_day` to select the timeframe. However, the excerpts do not establish whether bookings align to close date, booking date or effective date, or document the required join. The subscription acquisition dates and retention baseline date do not establish that mapping. - **Requested scope:** Global, 8 months, January–August 2026 inclusive. As a period query, it must not use `is_latest_available_date`. - **Next step:** Ask the Analytics team for the governed bookings measure, category dimensions, sales ownership fields, date mapping, joins and topic default filters. No query has been run or undocumented assumptions made. Warning: This answer was generated by AI and should be double checked.

Cost is the LLM completion spend LiteLLM priced for each call, summed per request. Chandler is running on the Codex CLI, which draws ChatGPT plan quota rather than per-token API billing, so this figure is not money paid — it is what the same traffic would have cost on the API, priced from the token counts Codex reports. Read it as the size of the bill avoided. Two known limits: embedding spend is not recorded, so retrieval and matching cost is missing, and because the figure is one sum per request it cannot be split by model within a request — a request's classifier and agent calls can use different models while llm_model holds only one name. Only authenticated calls are logged, USAGE_LOG_ENABLED can switch logging off, and log writes are fail-soft — this is not a complete record of traffic. Questions are grouped into sessions: a session is exact when the caller echoed its id back to us and otherwise inferred from a 30-minute gap in that user’s activity, so a grouping is only as good as the source shown on the session itself. A call with no attributable user gets no session at all; those questions are listed separately rather than dropped.