Skene
Product
Pricing
Docs
Blog
About
Log In
ProductPricingDocsBlogAbout
Log In
Resources / Glossary

Instrumentation surface

The total set of analytics calls in a codebase. The thing Skene reads, indexes, and watches for drift.

Concepts

About this term

This page is part of the Skene analytics instrumentation glossary. Use it as a reference when writing specs, dashboards, or playbooks.

Canonical glossary index: /resources/glossary

Glossary

Glossary

Analytics callEvent namePayload (event properties)Identify callEvent taxonomyInstrumentation surfaceBaseline manifestInstrumentation driftSemantic diffRemoved eventRenamed eventMoved eventAltered payloadConditional firing changeCustomer Data Platform (CDP)Schema registryMCP (Model Context Protocol)Coding agentSide effectFunnelConversion eventActivation eventCohort

Definition

The instrumentation surface is every analytics call that exists in your repo, considered together: each event name, each payload shape, each call site, each conditional that guards it. Most teams have never seen their full surface written down - it is implicit in the source files.

Why this concept matters

Treating instrumentation as a surface (something with shape and edges) is the move that lets you compare two states of it. Skene indexes the surface, then on every PR diffs the new surface against the indexed one.

Related terms

  • Baseline manifest
  • Instrumentation drift
Skene

Product

How it worksFeaturesArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

AboutOpen sourceContactPrivacyTerms
© 2026 Skene. All rights reserved.
Privacy PolicyTerms of Service
Skene