Welcome to TrackMe - Data in motion tracking system
TrackMe for Splunk is the ideal companion for your Splunk deployment, no matters the size of your environment, its unique capabilities help you on a daily basis to get the best value from your Splunk investments:
Discover and maintain Splunk entities at scale, track availability and quality of any kind of data in Splunk
Virtual tenancy is a key concept in TrackMe which allows creating on the fly knowledge objects in a repeatable way: create and scope tenants, experiment, destroy and restart as needed
TrackMe allows tracking your local Splunk deployment, or transparently any number of Splunk remote deployments (subject to licensing restrictions)
TrackMe’s unique workflow combines best Splunk capabilities, from a comprehensive user interface to notable events generation, SLA tracking and many more
Get the best from TrackMe components, using splk-feeds components provide deep Splunk feed tracking, splk-cim provides Common Information Model (CIM) compliance tracking, splk-flx (FLEX) adapts to any kind of Splunk magic query! (components are subjects to license restrictions)
Extend the visibility at any point in time with Hybrid and Elastic trackers, use Machine Learning outliers detection with deep and easy control, TrackMe is incredibly rich in features
License & support:
License, terms & conditions, support
Compatibility and download:
Requirements:
Installation:
Administration guide:
Administration guide
- Configuration
- Service Account and permissions
- Creating a service account for TrackMe with minimal permissions
- General Configuration
- Remote Splunk deployments accounts
- TrackMe Logging
- Indexes general settings
- Default Theme & Preferences Vtenants UI
- General configuration
- splk-general
- splk-data-sampling
- splk-outliers-detection
- 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 Parties Integration
- Outliers Anomaly Detection
- Machine Learning Outliers Anomaly Detection in TrackMe
- Data seasonality and behaviours
- Demonstrating Machine Outliers detection in TrackMe
- Accessing the ML models
- Accessing the ML models current results
- Disabling alerting on Outliers
- ML training scheduled jobs
- ML monitor scheduled jobs
- ML period exception: excluding periods of time
- ML Outliers system wide options
- ML Outliers options
- Understanding and Troubleshooting ML rendering results
- Troubleshooting ML training logs
- Troubleshooting ML rendering (monitoring) logs
- REST API endpoints for ML 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
- Feeds - Tags enrichments management
- CMDB Lookup Integration
- TrackMe CI/CD management (TCM)
User guide:
User guide
- Entities priority
- Entity Monitoring State
- Status Message
- Status Flipping Feature
- Notable Events
- Acknowledgments
- Splunk Feeds KPIs (splk-feeds)
- Splunk Feeds Thresholds (splk-feeds)
- 1. Introduction
- 2. Reviewing Current Thresholds
- 3. Defining Custom Threshold Values
- 4. Lagging Classes for Thresholds Management
- 5. Per Entity Thresholds
- 6. Simulating Threshold Values
- 7. Anatomy of an Entity suffering from index time Latency
- 8. Anatomy of an Entity with Delay with no Latency
- Conclusion
- Splunk Feeds Delayed & Inactive Entities (splk-feeds)
- Logical groups for Feeds tracking
- Splunk Workload (splk-wlk)
- Splunk SOAR Cloud & on-premise monitoring and active actions in TrackMe
- Cribl Logstream monitoring in TrackMe
Troubleshoot & FAQ:
Troubleshoot
Versioning and build history:
Versioning
Various
Various