TrackMe Logo

Quickstart

  • QUICK START - Starting with TrackMe: (feed tracking quickstart)

Use Cases Demo

  • Use Case Demo: This is All About Feeds
  • Use Case Demo: 360 Services Monitoring with TrackMe
  • Use Case Demo: Fields Quality (CIM and non-CIM)

License, terms & conditions, support

  • EULA License
  • Terms & Conditions
  • Support

Compatibility & Download

  • Compatibility
  • Download

Requirements

  • Requirements for TrackMe

Installation

  • Installation of TrackMe
  • Upgrading TrackMe
  • Migrate from TrackMe V1 to TrackMe V2
  • Migrating and Cloning TrackMe
  • License registration

Administration guide

  • Configuration
  • TrackMe theme for Tabulator
  • Large Scale Environment and Best Practices Configuration Guide
  • Creating Virtual Tenants
  • Manage Virtual Tenants
  • Operational Status Virtual Tenants
  • Scheduling Virtual Tenants
  • Personal user profile for Virtual Tenants
  • Splunk Remote Deployments (splunkremotesearch)
  • Role Based Access Control and ownership
  • Alerting Architecture & Third-Party Integration
  • Priority Management
  • Outliers Anomaly Detection
  • TrackMe Data Sampling - Events and Format Recognition for Quality Inspection in TrackMe
  • TrackMe Sourcetypes & Metrics
  • TrackMe REST API
  • splk-feeds - Creating and Managing Hybrid Trackers
  • Workload (splk-wlk) - Manage Workload tenants and trackers
  • splk-flx - Creating and managing Flex Trackers
  • splk-cim - Creating and Managing CIM Trackers
  • TrackMe Tags enrichment
  • Feeds (DataSource - splk-dsm) - Documentation Notes & Links
    • Introduction to Documentation Notes & Links for splk-dsm
    • Where to Find the Documentation Notes & Links in TrackMe UI
    • Defining Global Documentation Notes & Links
    • Defining Documentation Notes & Links Per Entity
    • REST API Endpoints
  • Pushing Expected Sources to TrackMe (Tracking Expected Sources or Hosts in splk-dsm/splk-dhm)
  • CMDB Lookup Integration
  • Elastic sources for feeds tracking
  • TrackMe CI/CD management (TCM)
  • Maintenance mode & knowledge database
  • TrackMe App on SOAR: Automate and interact with TrackMe from Splunk SOAR

White papers

  • TrackMe’s White Papers
  • Use Case Demo: This is All About Feeds
  • Use Case Demo: 360 Services Monitoring with TrackMe
  • Use Case Demo: Fields Quality (CIM and non-CIM)
  • Running a TrackMe Proof of Concept
  • QUICK START - Starting with TrackMe: (feed tracking quickstart)
  • Use TrackMe to detect abnormal events count drop in Splunk feeds
  • Analyse log messages logging level to detect behaviour anomalies using TrackMe’s Flex Object and Machine Learning Anomaly Detection
  • Tracking Splunk Cloud SVC consumption in TrackMe
  • Monitor Splunk Workload with TrackMe’s Workload component
  • Monitor Splunk Indexer Clusters
  • Monitor Splunk Search Head Clusters
  • Backing up and Restoring TrackMe
  • Auto deletion or management of TrackMe entities
  • Performing mass operations in TrackMe
  • Using SLA alerting to build a 2-tier monitoring system

User guide

  • Entities Priority
  • Entity Monitoring State
  • Status Message
  • Status Flipping Feature
  • Notable Events
  • Acknowledgments
  • Splunk Feeds KPIs (splk-feeds)
  • Splunk Feeds Thresholds (Delay and Latency, Machine Learning adaptive thresholding)
  • Splunk Feeds Delayed & Inactive Entities (splk-feeds)
  • Logical groups (entities ensemble association)
  • Splunk Workload (splk-wlk)
  • Splunk SOAR Cloud & on-premise monitoring and active actions in TrackMe
  • Cribl Logstream monitoring in TrackMe

Troubleshoot

  • Troubleshooting TrackMe
  • Frequently asked questions (FAQ)

Versioning

  • Release notes

Various

  • Third-party components credits
TrackMe
  • Feeds (DataSource - splk-dsm) - Documentation Notes & Links
  • View page source

Feeds (DataSource - splk-dsm) - Documentation Notes & Links

Introduction to Documentation Notes & Links for splk-dsm

Documentation Notes & Links

  • The documentation notes for splk-dsm provide easily accessible documentation context directly in the TrackMe UI

  • This feature is exclusively available for the Data Source tracking component (splk-dsm)

  • You can define global and default documentation notes and links, which apply to every entity in TrackMe

  • Additionally, you can define documentation notes and links for individual entities or link them to multiple entities

  • When both global and entity-specific documentation notes are defined, the entity-specific documentation notes take precedence

Where to Find the Documentation Notes & Links in TrackMe UI

When you open the screen of a specific entity, TrackMe shows at the top of the screen a link referring to documentation notes & links, depending on whether documentation notes have been defined yet (global or per entity):

No documentation notes defined yet:

screen001

Documentation notes defined:

screen002

If documentation notes are defined, the content would appear as:

screen003

If documentation notes are not defined yet, the following screen shows up and allows you to create a new documentation reference, or link to an existing documentation reference:

screen004

Defining Global Documentation Notes & Links

To define global documentation notes & links, navigate to the “Configure” screen and select the “splk-general” tab:

screen005 screen006

Example:

screen007 screen008

Note that the documentation notes & links defined globally can be overridden on a per-entity basis, so you can still reference specific documentation notes & links for each entity.

Before TrackMe 2.0.87

  • Prior to this release of TrackMe, the global configuration was managed through several Splunk macros (trackme_identity_card_default_url, trackme_identity_card_default_note)

  • If you were using this feature before this version, please migrate your configuration to the new global configuration screen

Defining Documentation Notes & Links Per Entity

If a global documentation reference is defined, TrackMe shows an informational message and allows defining an entity-specific documentation reference, or linking to an existing one:

screen009

If a specific entity note was defined, however, the screen will allow deleting or updating this reference:

screen010

REST API Endpoints

Identity cards are managed through read-only and write REST API endpoints. For detailed usage and examples, consult the REST API Dashboard in TrackMe:

API resource groups:

  • splk_identity_cards: read-only endpoints (requires trackmeuseroperations capability)

  • splk_identity_cards/write: write endpoints (requires trackmepoweroperations capability)

screen011
Previous Next

© Copyright © Copyright. 2022 - 2025. TrackMe Limited. All rights reserved. TRACKME® is a registered trade mark of TrackMe Limited, in both word and logo form. Any unauthorised use or reproduction of these marks is strictly prohibited and may result in legal action..

Built with Sphinx using a theme provided by Read the Docs.