What is TrackMe?

TrackMe is a Splunk app that discovers, maintains, and monitors the availability and quality of your data, and of the platform around it — across one Splunk deployment or many, at any scale.

Think of it as a control plane that sits on top of Splunk. It continuously reads what Splunk already holds and turns it into something you can actually operate on: per-entity health states for your data, findings for the platform around it — the people using Splunk, the forwarders, receivers and collectors carrying the data, the HEC endpoints receiving it and the Cribl pipelines in front of it — service-level objectives, stateful alerts, live topology maps and, optionally, AI-assisted investigation and triage.

What problem does it solve?

In a large Splunk environment, data silently breaks. A forwarder stops, a sourcetype starts arriving late, a field stops parsing, a scheduled search begins skipping. Splunk itself will not tell you — the searches simply return less, or nothing, and nobody notices until a detection misses or a dashboard goes blank.

The platform around the data fails just as quietly: an index doubles its licensed volume, an account runs all-time searches on a schedule nobody owns, two hundred forwarders drop behind a receiver tier, an intermediate forwarder pauses and holds every sender behind it, a database input stops collecting on a heavy forwarder that still reports, a HEC token goes silent behind a load balancer that still answers, a Cribl Destination backs up in front of Splunk.

TrackMe answers the questions that classic Splunk monitoring leaves open:

  • Is my data still flowing? Every data source, host, and metric feed is tracked for delay, latency, and volume.

  • Is my data still good? Field parsing quality and CIM compliance are monitored, not assumed.

  • Are my searches still healthy? Scheduled-search execution, skipping, and errors are tracked as first-class entities.

  • Is my license volume normal? Every index’s licensed volume is tracked for drops, spikes, inactivity and trend.

  • Who is doing what on Splunk? Accounts, their searches, their cost, their privileges and the knowledge objects they own.

  • Is my fleet forwarding? Every forwarding agent, connected or not, at any fleet size; the intermediate forwarders and the receivers, pool by pool.

  • Is every input collecting? The heavy forwarders and syslog collectors that run your add-on, scripted and file inputs, input by input.

  • Is the pipeline in front healthy? HEC endpoints, pools and tokens; Cribl Stream and Cribl Edge, from their own metrics and Leader.

  • Who do I tell, and how urgently? Priority, SLA, and impact scoring decide what is worth an alert and what is just noise.

Who is it for?

  • Splunk administrators who need to prove the platform is healthy and catch silent failures before users do.

  • SOC and detection engineers who depend on complete, timely, well-parsed data for their correlation searches.

  • Platform owners who answer for the licence, the usage and the forwarding tier.

  • Service owners who report availability and SLA attainment upward.

  • Managed service providers who operate many isolated customer environments from one place.

What can you monitor?

Everything tracked in TrackMe is an entity, and every entity belongs to one of seven monitoring components. The component decides what is measured. Seven dedicated tenant types — User Activity Monitoring, Splunk HEC, Splunk S2S, Splunk UF Fleet, Splunk Forwarder Collectors, Cribl Stream and Cribl Edge — raise findings instead of tracking entities (see Findings, Finding groups and findings actions).

Code

Component

What it tracks

DSM

Data Source Monitoring

(index, sourcetype) data feeds — delay, latency, volume, format quality.

DHM

Data Host Monitoring

Host × sourcetype activity — delay, latency, host count.

MHM

Metric Host Monitoring

Hosts sending metric data — metric lag per category.

VOL

Volume Outliers

The licensed volume of every index, read from the license usage logs — ML outliers (drops / spikes), inactivity, daily volume, trend and month projection.

FLX

Flex Objects

Any SPL you write, turned into a tracked entity with custom KPIs and dynamic thresholds.

FQM

Field Quality Monitoring

Field parsing quality and CIM compliance — coverage and success per field.

WLK

Workload Knowledge

Scheduled-search execution health — skip ratio, errors, execution delay.

UAM

User Activity Monitoring

Who is doing what on the platform — the accounts, their scheduled searches, their search activity and resource usage, read from the audit trail and the introspection and raised as findings. A dedicated tenant type rather than an entity component: see User Activity Monitoring.

Splunk HEC

Splunk HEC

The HTTP Event Collector endpoints of a Splunk deployment, their pools and tokens — availability, refused requests, back pressure, load balancing, rejected data, silent tokens — read from the HEC telemetry Splunk already writes and raised as findings. A dedicated tenant type: see Splunk HEC.

Splunk S2S

Splunk S2S

The receiving side of forwarding: the receivers, the intermediate forwarders and the pools they form — accepting or silent, back pressure and its origin, imbalance, churn, TLS and acknowledgement posture — read from the metrics and logs Splunk already writes and raised as findings. A dedicated tenant type: see Splunk S2S.

Splunk UF Fleet

Splunk UF Fleet

Every forwarding agent and the Deployment Servers that manage them, at any fleet size — connected or not, output blocked, destinations failing, restart loops, version drift, expected agents missing — read from the receivers and the agents’ own logs and raised as findings. A dedicated tenant type: see Splunk UF Fleet.

Splunk Forwarder Collectors

Splunk Forwarder Collectors

The forwarders used as collection points — heavy forwarders running add-ons, scripted and modular inputs, and the forwarders reading syslog files — and every input they run: inputs that stop, fail, go quiet or get disabled, blocked outputs, groups below their minimum. Raised as findings. A dedicated tenant type: see Splunk Forwarder Collectors.

Cribl Stream

Cribl Stream

The health and traffic of a Cribl Stream deployment — Sources, Destinations, Pipelines, Routes and Workers — read from the Cribl metrics in Splunk and the Cribl Leader API and raised as findings. A dedicated tenant type: see Cribl Stream and Cribl Edge.

Cribl Edge

Cribl Edge

The Fleets of a Cribl Edge Leader, their Edge Nodes and the Sources and Destinations they run — connectivity, rollouts and version drift, health, disk — read from the Leader API at any fleet size and raised as findings. A dedicated tenant type: see Cribl Edge.

The short version: DSM, DHM, and MHM answer “is the data arriving?”, FQM answers “is it well-formed?”, WLK answers “are my searches healthy?”, VOL answers “is my license volume normal?”, FLX lets you monitor anything else by writing the SPL yourself. Seven dedicated findings tenants complete the picture: UAM answers “who is doing what?”, a Splunk HEC tenant “are my HEC endpoints receiving, and who is refused?”, a Splunk S2S tenant “is my forwarding path healthy, pool by pool?”, a Splunk UF Fleet tenant “is every forwarding agent connected?”, a Splunk Forwarder Collectors tenant “is every input collecting?”, a Cribl Stream tenant “is my Cribl pipeline healthy?” and a Cribl Edge tenant “is every Edge Node where it should be?”.

The seven TrackMe monitoring components and the seven dedicated findings tenants, grouped by the question each answers Top row, the seven entity components in five columns: "Is the data arriving?" groups DSM, DHM and MHM; "Is it well-formed?" is FQM; "Are searches healthy?" is WLK; "Is my license volume normal?" is VOL; "Anything else?" is FLX, where you write the SPL. Below, the dedicated findings tenants, which raise findings instead of tracking entities: User Activity Monitoring answers "Who is doing what?", Splunk HEC "Are my endpoints receiving?", Splunk S2S "Is my data path healthy?", Splunk UF Fleet "Is every agent connected?", Splunk Forwarder Collectors "Is every input collecting?", Cribl Stream "Is my Cribl pipeline healthy?" and Cribl Edge "Is every Edge Node in place?"; a last card lists what the seven share: policies, findings and Finding groups, assignment rules and notifications, findings actions and webhooks, and an AI Agent per tenant type. Seven components and seven findings tenants — grouped by the question each one answers Is the data arriving? DSM Data Source Monitoring index × sourcetype feeds DHM Data Host Monitoring host × sourcetype activity MHM Metric Host Monitoring hosts sending metric data delay · latency · volume Is it well-formed? FQM Field Quality Monitoring parsing quality & CIM Is every field parsed and CIM-compliant? Coverage & success measured per field. Are searches healthy? WLK Workload Knowledge scheduled-search health Are searches skipping, erroring, or running late? Execution health as first-class entities. Is my license volume normal? VOL Volume Outliers licensed volume per index Is an index dropping, spiking, or going silent? ML outliers, inactivity, trend & month projection. Anything else? FLX Flex Objects any SPL → tracked entity Everything else — you write the SPL; it becomes an entity with custom KPIs & dynamic thresholds. Dedicated findings tenants — one tenant type each: findings and Finding groups, not entities Who is doing what? UAM User Activity Monitoring accounts, searches, knowledge objects Who runs what, owns which schedule, holds privileges or eats the CPU. Are my endpoints receiving? Splunk HEC HTTP Event Collector endpoints, pools and tokens Refused senders, back pressure, imbalance, tokens gone silent. Is my data path healthy? Splunk S2S Receivers and intermediates pools, senders, the S2S data path Blocked queues and their cause, silent receivers, imbalance. Is every agent connected? Splunk UF Fleet Forwarding agents groups and Deployment Servers Disconnections at any fleet size, mass events as one finding. Is every input collecting? Splunk Forwarder Collectors Collection points and their inputs add-ons, scripted, modular, syslog Inputs that stop, fail or go quiet, groups below their minimum. Is my Cribl pipeline healthy? Cribl Stream Sources, Destinations, Routes, Workers Cribl metrics in Splunk + Leader API Backpressure, traffic outside what each object learned, Workers that drift. Is every Edge Node in place? Cribl Edge Fleets, Edge Nodes, Sources, Destinations Leader node directory, any fleet size Disconnected nodes, version drift, failing inputs and full disks. Shared by all seven Policies, findings and Finding groups, assignment rules and notifications, findings actions and webhooks, and an AI Agent per tenant type.

Each component is covered in Part 3 — Monitoring Components.

How TrackMe is built

TrackMe is organised around three layers. You do not need to know the internals to use it, but the shape explains why the product behaves the way it does.

Layer

What it does

Data plane

Scheduled searches (“trackers”) run on a cycle and a shared decision maker computes each entity’s state and score. This is where “is it healthy?” is decided. Findings tenants run their own collection and policy jobs instead.

Control plane

A REST API and a per-tenant KV Store hold all configuration and current state — the single source of truth.

Presentation

A modern React interface (Virtual Tenants, Tenant Home, the findings workspaces, Topology Studio) and an optional AI Assistant.

The mechanics of the cycle are explained in How TrackMe works.

Editions and licensing

TrackMe ships in several editions (Foundation, Enterprise, Unlimited, and trial / developer variants). A new install automatically starts a 90-day Foundation Trial with full functionality. When a license expires, TrackMe enters read-only mode: monitoring keeps running and all data, dashboards, alerts, and history stay visible, but creating or editing configuration is disabled until a license is applied.

See the License page for the full edition matrix and the License registration page to apply one.

See also