Does a recorded LangSmith LLM trace necessarily have a calculable cost
Does a recorded LangSmith LLM trace necessarily have a calculable cost?
Automatic cost calculation needs token counts, model and provider identification, and applicable model pricing. A recorded trace alone does not establish that those inputs were supplied.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Treat absent cost as unknown until the usage and pricing inputs are reconciled; it is not evidence of free execution.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can the displayed model label alone establish which LangSmith pricing rule was applied
Can the displayed model label alone establish which LangSmith pricing rule was applied?
LangSmith model pricing uses a model-name match pattern and optional provider match. Reviewing the actual metadata and matching entry is necessary when custom names or gateways change model labels.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Do not accept a calculated amount as the applicable contracted price without checking the matching rule.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a generic per-token LangSmith price map cover every custom charging formula
Does a generic per-token LangSmith price map cover every custom charging formula?
LangSmith documents built-in support for specified Gemini stepwise pricing. For other non-linear models it directs clients to calculate cost and send the result in usage metadata.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Do not equate a linear estimate with a non-linear contracted charge without the applicable calculation evidence.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does adding a thread identifier only to the parent preserve all child cost totals
Does adding a thread identifier only to the parent preserve all child cost totals?
LangSmith requires thread metadata on child runs as well as the parent for thread filtering and token or cost aggregation. Unlabelled children can be omitted from that thread view.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Do not treat the thread total as complete until child metadata coverage is checked.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does reaching a LangSmith evaluator budget stop the underlying agent
Does reaching a LangSmith evaluator budget stop the underlying agent?
The documented cap pauses evaluation on the affected project or dataset. The agent and its trace continue; the missing scores do not establish that application execution stopped.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Keep evaluator availability and application execution separate when reviewing budget effects.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Is an evaluator weekly cap an exact ceiling on every in-flight charge
Is an evaluator weekly cap an exact ceiling on every in-flight charge?
LangSmith records spend after each evaluator run finishes. Concurrent in-flight runs can therefore push the final amount above the effective cap before new evaluations are paused.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Retain in-flight completion and cost evidence before asserting an exact maximum.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Will LangSmith automatically score runs skipped while an evaluator was budget-paused
Will LangSmith automatically score runs skipped while an evaluator was budget-paused?
After a reset or increased limit, evaluation resumes on new runs. The documentation states that skipped runs are not backfilled, leaving a distinct assessment coverage gap.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Do not treat budget recovery as completion of the previously skipped evaluation interval.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does changing the organisation evaluator limit update every attachment
Does changing the organisation evaluator limit update every attachment?
Changing the organisation default updates attachments that inherit it. Custom per-project or per-dataset overrides remain in place; clearing the default removes caps only from inheriting attachments.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Inspect effective attachment limits before claiming a uniform organisation budget policy.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does LangSmith evaluator spend independently verify the provider invoice
Does LangSmith evaluator spend independently verify the provider invoice?
Evaluator spend is calculated from configured model prices, not provider billing. Discounts, custom contracts and unconfigured variants can produce differences from an invoice.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Reconcile pricing assumptions and provider evidence before treating a difference as incorrect billing or settlement.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does LANGSMITH_TRACING=true prove every invocation was recorded
Does LANGSMITH_TRACING=true prove every invocation was recorded?
Scoped tracing_context settings take precedence over global configuration and environment variables. Nested contexts use the innermost setting, so tracing can be disabled for selected invocations despite a global enable flag.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Inspect runtime contexts before interpreting absent traces as absent execution.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a LangSmith SDK sampling setting control every ingestion path
Does a LangSmith SDK sampling setting control every ingestion path?
The documented sampling configuration applies to the SDK or LangChain, not direct API logging. Individual clients can also have different rates, so one environment value does not describe every producer.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Inventory producer paths and effective client rates before comparing captured activity.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does changing a Langfuse model price necessarily change an explicitly supplied cost
Does changing a Langfuse model price necessarily change an explicitly supplied cost?
Langfuse distinguishes ingested usage or cost from inferred values. When both are available, ingested values take priority, so the recorded amount may reflect the supplied payload rather than model-price inference.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Identify the amount origin before diagnosing pricing or reconciliation discrepancies.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can cached input tokens be counted both within input and in a separate Langfuse usage bucket
Can cached input tokens be counted both within input and in a separate Langfuse usage bucket?
Langfuse treats usage keys as non-overlapping buckets. Overlapping counts can double-count usage and inferred cost; directly ingested cost values are not recalculated by that overlap.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Reconcile bucket definitions before accepting totals or alleging duplicate billing.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can a custom Langfuse model definition override a maintained default price
Can a custom Langfuse model definition override a maintained default price?
Langfuse matches model names using regular expressions and gives user-defined models priority over maintained definitions. A familiar model label does not establish which pricing definition supplied the estimate.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Inspect the matching custom definition before relying on a maintained default price assumption.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does updating a Langfuse pricing definition repair costs on older generations
Does updating a Langfuse pricing definition repair costs on older generations?
The documented model-definition changes apply to generations logged afterward. Updating a price is not evidence that historical amounts have been recalculated.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Keep historical estimates versioned and reconcile them separately rather than silently treating them as corrected.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does every Langfuse observation type contribute native usage and cost
Does every Langfuse observation type contribute native usage and cost?
Langfuse documents cost and usage on generation and embedding observations. Other observation types do not carry those fields, so a visible tool or workflow observation is not necessarily priced.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Do not call the visible trace total a complete business-task bill without separately accounting for excluded charges.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does Langfuse masking sanitize the same spans sent to every other backend
Does Langfuse masking sanitize the same spans sent to every other backend?
The Python mask_otel_spans hook affects the Langfuse client export. A separate OpenTelemetry exporter receives its own unmodified copy unless its path has separate masking.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Review every exporter path before asserting that sensitive telemetry is redacted everywhere.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can a masking error cause Langfuse telemetry to disappear
Can a masking error cause Langfuse telemetry to disappear?
An exception or invalid overall masking result drops the export batch. An invalid span patch drops that span; invalid returned attribute values remove the affected attribute. These failure scopes differ.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Retain masking-error evidence before interpreting missing spans or fields as no activity.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does the legacy Langfuse Python mask hook inspect final third-party OpenTelemetry attributes
Does the legacy Langfuse Python mask hook inspect final third-party OpenTelemetry attributes?
The legacy mask hook transforms data set through Langfuse SDK APIs at attribute creation. It does not inspect final raw OpenTelemetry attributes from third-party instrumentation.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Do not use that hook alone as evidence that third-party span data is sanitized.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can mask_otel_spans redact every field of a Langfuse span
Can mask_otel_spans redact every field of a Langfuse span?
The hook can change span attributes but not names, identifiers, parent relationships, resource attributes, events, links or instrumentation scope. Its configured presence is not whole-span sanitization.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Keep sensitive information out of excluded fields and inspect their separate handling.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can Python multi-project Langfuse routing isolate every third-party span by project
Can Python multi-project Langfuse routing isolate every third-party span by project?
The documented experimental routing uses a Langfuse public-key attribute. Third-party spans lacking it, if accepted by export filters, can be processed by all configured project processors.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Verify instrumentor, filter and routing coverage before claiming tenant isolation.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does flushing a request-scoped Langfuse provider include spans that end later
Does flushing a request-scoped Langfuse provider include spans that end later?
The documented request-scoped JS/TS pattern exports ended spans at shutdown. Observations ending after the request callback finishes are lost, including unfinished streaming or background work.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- End relevant observations before shutdown and check export results; flush invocation alone is insufficient.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does a request-scoped Langfuse routing provider also route global OpenTelemetry instrumentation
Does a request-scoped Langfuse routing provider also route global OpenTelemetry instrumentation?
Third-party libraries using the global tracer provider do not pass through the request routing provider. Integrations accepting an explicit tracer need the intended routing tracer supplied.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Keep globally emitted spans outside a request-project completeness claim until their export path is established.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Can shared background work be attributed to the wrong Langfuse project
Can shared background work be attributed to the wrong Langfuse project?
The documented JS/TS request-routing pattern warns that a shared queue can execute under whichever request context is active when it drains. Spans can then be routed to that request project.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Bind work to the originating async context before treating project attribution as reliable.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review
Does code outside a Langfuse request context fall back safely into the same project
Does code outside a Langfuse request context fall back safely into the same project?
In the documented request-scoped pattern, spans started outside its context are dropped. Long-lived callbacks and stored observation handles can lose the request context unless correctly bound.
Documentation reviewed 2026-10-30. Primary source.
Boundaries
- Do not infer no execution from absence of out-of-context spans; inspect callback context propagation.
- Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.
- No expanded capabilities or licences for existing INDEX executables.
Complete record JSON · Exact free preview JSON · Source review