- Introduction
- Getting Started
- Dashboard
- Events Management
- Insights
- Catalog
- Drifts Management
- RPA Usage
- Locks
- Links
- Advanced Features
Tracker is a comprehensive event management platform designed to monitor and visualize deployments, operations, configuration drifts, and RPA activities across your infrastructure.
- Real-time event tracking across multiple environments
- Overlap detection to identify scheduling conflicts
- Gantt-style visualization for timeline planning
- Jira integration for drift management
- Advanced filtering and search capabilities
- Dark mode support for comfortable viewing
Navigate to your Tracker instance URL (e.g., https://tracker.your-domain.com)
The interface uses a collapsible sidebar on the left with four sections:
- Dashboard - Overview of today's activity
- Timeline - Chronological list of events
- Streamline - Gantt chart view
- Calendar - Monthly calendar
- Overlaps - Conflict management
- Insights - Analytics and statistics over a configurable period
- Catalog - Service inventory
- Architecture - Service dependency visualization
- Compliance - Version compliance tracking
- Drifts - Configuration drift tracking
- RPA Usage - Automation monitoring
- Locks - Deployment and operation locks
- Links - Quick access portal to tools and resources
- Docs - In-app documentation
- Collapse sidebar button (top of sidebar) to hide/show the sidebar
- Events Channel Slack link at the bottom of the sidebar
The top header provides:
- Search bar (
Ctrl+Kor⌘K) - Global search across all data - Quick action buttons: New Lock, New Drift, New RPA, New Service, New Event
Three theme modes are available at the bottom of the sidebar:
- Light mode
- Dark mode
- System mode (follows OS preference)
The Dashboard (/dashboard) provides a real-time overview of today's events and system health.
Four main metrics are displayed:
- Total Events - All events created today (with in-progress count)
- Success Rate (%) - Percentage of successfully completed events
- Critical Failures - Failed or errored events (with active failure indicator)
- Overlaps - Number of scheduling conflicts detected
A 24-hour bar chart showing events per hour with a Live indicator. Allows quick identification of activity peaks throughout the day.
A pie chart showing the distribution of today's events by environment (Production, Pré-production, UAT / Recette, Dev / Integration) with percentages and counts.
A filterable table showing recent events with the following columns:
- Event ID - Short hash identifier
- Title - Event description
- Type - Deployment, Operation, RPA Usage, etc.
- Service - Affected service
- Environment - Deployment environment
- Priority - P1 (Critical) to P5 (Low)
- Status - Planned, Success, Failed, Warning, etc.
- Timestamp - Creation time
Above the table, filter buttons let you narrow results instantly:
- Type: Deployment, Operation, Drift, Incident
- Status: Success, Failed, In Progress, Warning, Open, Planned
- Env: Prod, Preprod, Dev
Click "View Historical Data Archive" to go to the full Timeline view.
Purpose: Chronological list of all events with advanced filtering
Navigate through time using:
- Period selector - Choose 1, 3, 7, 14, 30, 60, or 90 days
- Previous/Next buttons - Move backward or forward by the selected period
- Today button - Jump back to the current period
Toggle between:
- Newest first (default) - Most recent events at the top
- Oldest first - Historical events first
Click the Filters button to access:
- Event Type - Deployment, Operation, Drift, Incident
- Environment - Development, Integration, Production, etc.
- Priority - P1 (Critical) to P5 (Low)
- Status - Start, Success, Failure, Error, Done, etc.
- Service - Filter by specific services from the catalog
Active filters are indicated by:
- Blue highlight on the Filters button
- Badge showing the number of active filters
- Summary text below the page title
Each event displays:
- Type icon and badge - Color-coded by event type
- Title - Event description
- Service name - In a monospace badge
- Badges - Environment, Priority, Status
- Timestamp - When the event was created
- Links - To source systems (Slack, GitHub, etc.)
Click any event card to open the detailed modal.
Purpose: Gantt-style visualization to identify scheduling conflicts
Groups:
- By Service - Events grouped by project/service
- By Environment - Events grouped by environment
Time Scale:
- Week View - 7 columns (one per day)
- Day View - 24 columns (one per hour)
Groups with overlapping events show:
- 🚨 Animated warning icon (pulsing orange triangle)
- Concurrent count - Number of simultaneous events
- Multi-track layout - Events automatically placed on separate tracks to avoid visual overlap
- Previous/Next buttons - Navigate by the selected period
- Today button - Return to current period
- Period selector - 1, 3, 7, 14, or 30 days
Events are displayed as colored bars showing:
- Duration - Bar length represents event duration
- Type - Color indicates event type
- Title - Truncated to fit
- Time - Start time shown for longer events
Click any event bar to view full details.
Same advanced filtering as Timeline view.
Purpose: Monthly calendar with daily event overview
- Current day highlighted in blue
- Selected day highlighted in primary color
- Days with overlaps show a warning icon 🚨
Click any day to view its events in the right panel.
When a selected day has overlapping events:
- Orange alert banner appears at the top
- List of conflicts with exact time periods
- Event pairs showing which events overlap
- Duration details for each event
Events on the selected day show:
- Orange background if involved in an overlap
- Warning icon for conflicting events
- Time range (HH:mm - HH:mm) for each event
- All badges - Type, Environment, Priority, Status
- Links to source systems
Same advanced filtering as other event views.
Purpose: Dedicated page for managing scheduling conflicts
Three key metrics:
- Total Overlaps - Number of conflicts in the period
- Days with Overlaps - How many days are affected
- Services Involved - Number of unique services
- Period selector - 1, 3, 7, 14, or 30 days
- Navigation buttons - Previous/Next/Today
- Date range display - Shows current period
For each day with overlaps:
Overlap Information:
- Time period - Exact overlap window (HH:mm - HH:mm)
- Duration - Length of conflict in minutes
Side-by-Side Comparison: Two cards showing each conflicting event:
- Event type and environment badges
- Title (clickable for details)
- Service name
- Start and end times
Contact Information: If the service is in the catalog:
- Owner name - Team or person responsible
- Email - Clickable mailto: link
- Slack channel - Direct link to team channel
Use this page to:
- Identify scheduling conflicts
- Contact responsible teams
- Coordinate deployment windows
- Avoid production incidents
Purpose: Analytics and statistics on event activity over a configurable period
- Environment - Filter by a specific environment (default: All)
- Service - Filter by a specific service (default: All)
- Period - Configurable period (default: last 30 days)
Four event type breakdowns with count and percentage:
- Deployments
- Incidents
- Operations
- Drifts
- Top Projects - Most active projects during the period
- Event Distribution - Visual breakdown of event types and statuses
Purpose: Inventory of all modules, libraries, and projects
Type to search across:
- Service name
- Description
- Owner name
Clear button (X) appears when text is entered.
Click badges to filter by:
- Module
- Library
- Workflow
- Project
- Chart
- Package
- Container
Active filters show in blue.
Click badges to filter by programming language:
- Go, Java, Python, PHP
- JavaScript, TypeScript, Rust
- Terraform, Helm, Docker
- And more...
Each badge shows the language icon.
- Click multiple filters to combine them
- Clear All button appears when filters are active
- Result count updates in real-time
Columns:
- Name - Service identifier with package icon
- Type - Badge showing catalog type
- Language - Badge with language icon
- Version - Current version number
- Owner - Team or person responsible
- Description - Brief description (truncated)
- Links - Icons for repository and documentation
Click "New Service" in the header to register a new service.
Purpose: Visualize service dependencies and relationships
Accessible at /catalog/dependencies. Displays an interactive dependency graph of services registered in the catalog, with a Legend explaining the visual indicators.
Purpose: Track which projects use outdated versions of their declared deliverables
Accessible at /catalog/version-compliance.
- Total Projects - All projects in the catalog
- Compliant - Projects using up-to-date deliverable versions
- Non-Compliant - Projects with at least one outdated deliverable
- No Deliverables - Projects without declared deliverables
- Search - Filter by project or deliverable name
- Type - Package, Chart, Container, Module
Columns:
- Project - Project name
- Status - Compliant / Non-Compliant / No Deliverables
- Compliance - Percentage of up-to-date deliverables
- Deliverables - Total count of declared deliverables
- Outdated - Count of outdated deliverables
- Actions - View Details button
Purpose: Track and manage configuration drifts
Three cards showing:
- Total Drifts - All detected drifts
- Unresolved - Drifts not yet fixed
- Resolved - Completed drifts
Each drift displays:
- Status badge - Resolved (green) or In Progress (yellow)
- Title - Drift description
- Message - Detailed drift information (scrollable)
- Service - Affected service in monospace badge
- Source - Detection source
- Environment - Where drift was detected
- Owner - Responsible person/team
- Timestamp - When drift was detected
- Click "Add Ticket" button on any drift
- Modal opens with drift information
- Click "Open Jira (New Tab)" to create a ticket
- Title and description are pre-filled
- Create the ticket in Jira
- Copy the ticket URL
- Paste it in the "Jira Ticket URL" field
- Click "Save Ticket Link"
- Linked tickets appear as clickable links
- External link icon indicates it opens in a new tab
- Click to view the ticket in Jira
Click "Update Ticket" to change the linked ticket URL.
Filter drifts by:
- Environment
- Priority
- Status
- Service (from catalog)
Click "New Drift" in the header bar to manually create a drift event.
Purpose: Monitor Robotic Process Automation activities
Three cards showing:
- Total Operations - All RPA operations
- Success - Successful executions
- Failures - Failed operations
Each RPA operation displays:
- Type badge - Operation type
- Title - Operation description
- Service - RPA service name
- Environment - Execution environment
- Status badges - Priority and Status
- Timestamp - Execution time
Same filtering capabilities as other event views.
Click "New RPA" in the header bar to manually create an RPA event.
Purpose: View and manage deployment and operation locks across services
Accessible at /locks.
Three summary cards:
- Total Locks - All active locks
- Unique Services - Number of distinct services with locks
- Environments - Number of environments affected
Columns:
- Service - Locked service name
- Environment - Environment where the lock applies
- Resource - Type of locked resource (deployment, operation, etc.)
- Locked By - Username or team that acquired the lock
- Created At - Date and time the lock was created
- Duration - Time elapsed since lock creation
- Actions - Unlock button to release the lock
Click "New Lock" in the header bar to acquire a new lock.
Purpose: Quick access portal to all your tools and resources, synced from Homer
Accessible at /links.
- Filter bar (
Ctrl+K) - Filter links by name - Refresh button - Reload links from Homer
- Add Link button - Manually add a local link
Links are organized by categories (e.g., team names, tool groups). When Homer is unavailable, local links are shown instead.
Click any event to open a detailed modal showing:
Header:
- Event type icon and badge
- Title
- Close button (X)
Information Sections:
- Service - Service name
- Source - Event source system
- Environment - Deployment environment
- Owner - Responsible person/team
- Priority - Event priority level
- Status - Current status
- Dates - Start and end times (if applicable)
Message:
- Full event message or description
- Scrollable if long
Links:
- All associated links (Slack, GitHub, etc.)
- Appropriate icons for each source
- Open in new tabs
Metadata:
- Event ID
- Creation timestamp
- Last update time
- Start broad - View all events first
- Add filters gradually - Narrow down step by step
- Use multiple filters - Combine for precise results
- Check active count - Badge shows how many filters are active
- Clear when done - Use "Clear All Filters" to reset
- Ctrl+K / ⌘K - Open global search
- Escape - Close modals
- F5 - Refresh page
- Ctrl/Cmd + F - Browser search (works in tables)
- Use time period filters to limit data
- Apply service filters for faster loading
- Clear filters when not needed
- Refresh page if data seems stale
Tracker is responsive and works on mobile devices:
- Navigation collapses to hamburger menu
- Cards stack vertically
- Badges wrap to multiple lines
- Touch-friendly buttons and links
- Check time period selection
- Verify filters are not too restrictive
- Ensure events exist for the selected period
- Try "Clear All Filters"
Overlaps are detected when:
- Events have start and end dates
- Time periods actually overlap
- Events are in the selected time range
- Verify Jira domain is configured
- Check you're logged into Jira
- Ensure ticket URL is correct
- Contact admin if domain is not set
- Refresh the page
- Clear browser cache
- Check console for errors (F12)
- Report issue to admin
- Check Dashboard daily for overview
- Use Streamline to plan deployments
- Monitor Overlaps to avoid conflicts
- Link Jira tickets to drifts
- Filter by your services for focus
- Review Insights for trends over 30 days
- Check overlap page for coordination issues
- Monitor drift resolution times
- Use calendar view for planning
- Check Compliance to track outdated deliverables
- Coordinate via Overlaps page before deploying
- Update catalog with accurate contact info
- Link tickets for traceability
- Use consistent naming for services
- Document in event messages for context
- Use Locks to prevent concurrent deployments
- Documentation - Check
/docsfolder - GitHub Issues - Report bugs or request features
- Team Chat - Contact DevOps team
- Email - support@your-domain.com
Include:
- Page where issue occurred
- Steps to reproduce
- Expected vs actual behavior
- Screenshots if applicable
- Browser and version
Submit via:
- GitHub Issues with "enhancement" label
- Team feedback channel
- Direct message to DevOps team
Architecture - Interactive visualization of service dependencies and relationships
Compliance - Tracking whether projects use up-to-date versions of their declared deliverables
Drift - Unintended configuration change detected in infrastructure
Event - Any tracked activity (deployment, operation, incident, etc.)
Insights - Analytics view showing event distribution and trends over a configurable period
Lock - A mechanism to prevent concurrent deployments or operations on a service
Overlap - Two or more events running simultaneously
RPA - Robotic Process Automation
Service - Application, module, or system being tracked
Streamline - Gantt-style timeline visualization
P1-P5 - Priority levels (P1 = Critical, P5 = Low)
Last Updated: April 2026 Version: 2.0