Overview
Wazuh Dashboard Plugins organize security data into specialized index patterns optimized for different types of events and states. This structured approach enables efficient querying, visualization, and analysis of security telemetry.Index Pattern Architecture
Data is organized into three primary categories:Events
Real-time security events with timestamps, categorized by event type
States
Current state snapshots of system inventories, vulnerabilities, and configurations
Operational
Monitoring data and statistics for agents and servers
Index Pattern Types
Fromconstants.ts:19-108:
Events Index Patterns
Events represent time-series security data with the@timestamp field.
- Primary Events
- System Activity
- Security Events
- Access Management
- Applications
- Network Activity
- Other Events
Pattern:
Type:
Time Field:
Health Check:Required Fields:
wazuh-events*Type:
eventsTime Field:
@timestampHealth Check:
index-pattern:eventsThe main index pattern that aggregates all event types. Used for cross-category searches and general event exploration.Cloud Services Events
Specialized event patterns for cloud provider monitoring:Generic Cloud Services
Generic Cloud Services
Pattern:
Health Check:
wazuh-events-v5-cloud-services*Health Check:
index-pattern:events-cloud-servicesAggregated cloud service events across all providers.Known Fields: common/known-fields/events-cloud-services.jsonAWS
AWS
Pattern:
Health Check:Known Fields:
wazuh-events-v5-cloud-services-aws*Health Check:
index-pattern:events-cloud-services-awsAmazon Web Services specific events:- CloudTrail API calls
- GuardDuty findings
- Config changes
- VPC Flow Logs
common/known-fields/events-cloud-services-aws.jsonAzure
Azure
Pattern:
Health Check:
wazuh-events-v5-cloud-services-azure*Health Check:
index-pattern:events-cloud-services-azureMicrosoft Azure events:- Azure AD logs
- Activity logs
- Security Center alerts
common/known-fields/events-cloud-services-azure.jsonGCP
GCP
Pattern:
Health Check:
wazuh-events-v5-cloud-services-gcp*Health Check:
index-pattern:events-cloud-services-gcpGoogle Cloud Platform events:- Cloud Audit Logs
- Security Command Center
- IAM policy changes
common/known-fields/events-cloud-services-gcp.jsonStates Index Patterns
States represent current snapshots of system configurations and inventories (no time field).- Vulnerabilities
- File Integrity Monitoring
- Security Configuration Assessment
- IT Hygiene (Inventory)
Pattern:
Type:
Health Check:Known Fields:
wazuh-states-vulnerabilities*Type:
states-vulnerabilitiesHealth Check:
index-pattern:states-vulnerabilitiesCurrent vulnerability state of systems:- Detected CVEs
- Affected packages
- Severity scores (CVSS)
- Fix availability
common/known-fields/states-vulnerabilities.jsonOperational Index Patterns
- Agent Monitoring
- Server Statistics
Pattern:
Type:
Time Field:
Health Check:Known Fields:
wazuh-monitoring*Type:
monitoringTime Field:
timestampHealth Check:
index-pattern:monitoringAgent status and metrics:- Agent connectivity status
- Last keep-alive timestamp
- Agent version information
- Configuration sync status
common/known-fields/monitoring.jsonIndex Pattern Initialization
The server plugin registers health checks to ensure all index patterns exist during startup.Health Check Registration
Fromplugins/main/server/plugin.ts:
Index Pattern Options
string
required
Unique identifier for the health check task
string
required
The index pattern string (e.g.,
wazuh-events*)object
Saved object properties to set/override
boolean
default:"false"
Whether the index pattern has a time field
array
Known field definitions when indices don’t exist yet
boolean
default:"false"
Whether this should be the default index pattern
Known Fields
Known fields are pre-defined field mappings stored in JSON files undercommon/known-fields/. These allow index patterns to be created before any data is indexed.
Example: common/known-fields/events.json
Data Flow
Event Pipeline
1
Agent Collection
Wazuh agents collect security events and system state data
2
Manager Processing
Wazuh Manager processes, enriches, and categorizes events
3
Indexing
Events are indexed into OpenSearch with appropriate index patterns
4
Index Pattern Matching
Dashboard queries use index patterns to search relevant indices
5
Visualization
Results are rendered in dashboards and visualizations
Index Naming Convention
wazuh: Namespace prefix{category}: events, states, monitoring, statistics{version}: v5 (for events){subcategory}: security, system-activity, vulnerabilities, etc.{date}: YYYY.MM.DD for daily indices
Sample Data
The plugin provides sample data generation for testing and demonstrations.Sample Data Categories
Fromconstants.ts:271-475:
- Agent Monitoring
- Security Alerts
- Auditing & Policy Monitoring
- Threat Detection
- File Integrity Monitoring
- Security Configuration Assessment
- Inventory Agent
- Server Statistics
- Vulnerabilities
Sample Data Configuration
number
default:"1500"
Default number of sample documents to generate
Query Optimization
Time-Based Filtering
For event index patterns, always apply time range filters:Agent Filtering
Filter by specific agent:Cluster Mode Filtering
For vulnerabilities in cluster mode:Field Formats
Specialized field formatting improves data presentation:Byte Formatting
Percentage Formatting
Integer Formatting
Index Lifecycle Management
Index patterns use wildcard matching, allowing for index rotation and lifecycle policies without reconfiguration.
wazuh-events* matches:
wazuh-events-v5-security-2026.03.01wazuh-events-v5-security-2026.03.02wazuh-events-v5-security-2026.03.03wazuh-events-v5-security-2026.03.04
- Daily index rotation
- Automated retention policies
- Hot-warm-cold architecture
- Index deletion without breaking dashboards
Configuration
Default Index Pattern
Set the default index pattern for initial searches:wazuh-events*) is typically set as default.
Time Field Configuration
For time-series data:Time Filter Settings
Default time range for dashboards:Best Practices
Use Specific Patterns
Query the most specific index pattern for your use case (e.g.,
wazuh-events-v5-security* instead of wazuh-events*) for better performanceApply Time Filters
Always filter by time range on event indices to limit data scanned
Filter Early
Apply agent, cluster, and category filters in the query for index-level filtering
Aggregate Wisely
Use appropriate aggregation intervals and bucket limits
Index Pattern Reference
Complete Index Pattern List
Events (12 patterns)
Events (12 patterns)
wazuh-events*wazuh-events-v5-system-activity*wazuh-events-v5-security*wazuh-events-v5-access-management*wazuh-events-v5-applications*wazuh-events-v5-network-activity*wazuh-events-v5-other*wazuh-events-v5-cloud-services*wazuh-events-v5-cloud-services-aws*wazuh-events-v5-cloud-services-azure*wazuh-events-v5-cloud-services-gcp*
States (20 patterns)
States (20 patterns)
wazuh-states-vulnerabilities*wazuh-states-fim*wazuh-states-fim-files*wazuh-states-fim-registry-keys*wazuh-states-fim-registry-values*wazuh-states-sca*wazuh-states-inventory*wazuh-states-inventory-system*wazuh-states-inventory-hardware*wazuh-states-inventory-networks*wazuh-states-inventory-packages*wazuh-states-inventory-ports*wazuh-states-inventory-processes*wazuh-states-inventory-protocols*wazuh-states-inventory-users*wazuh-states-inventory-groups*wazuh-states-inventory-services*wazuh-states-inventory-interfaces*wazuh-states-inventory-hotfixes*wazuh-states-inventory-browser-extensions*
Operational (2 patterns)
Operational (2 patterns)
wazuh-monitoring*wazuh-statistics*
Related Pages
Architecture
System architecture and data flow
Security Modules
Security modules that use these data sources
Plugin System
Plugin lifecycle and health checks
Query Guide
Learn how to query and visualize data