If an alert appears in /var/ossec/logs/alerts/alerts.json but not in the Wazuh dashboard, Wazuh generated and wrote the alert locally—but that does not prove the indexer stored it. Follow the document from the alert file through the forwarding connector to the indexer, then use the bulk response and logs to find where it failed. A field represented as an object in one alert and a scalar in another is one possible mapping conflict, not a diagnosis you can make from HTTP 400 alone.
How an alert reaches the dashboard
Wazuh’s documentation says the server analyzes events from monitored endpoints and generates alerts when events match detection rules. By default, alert data is written to /var/ossec/logs/alerts/alerts.json and /var/ossec/logs/alerts/alerts.log. The server then forwards the JSON alert document from alerts.json to the Wazuh indexer API, which stores alerts in wazuh-alerts-* indices. Wazuh indexer indices
As an Amazon Associate I earn from qualifying purchases.
That creates two distinct troubleshooting states: the alert file shows that generation and local writing occurred; the bulk API response and indexer logs show whether indexing succeeded. A file entry alone cannot establish that the document was accepted or that it is available to the dashboard.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What HTTP 400 tells you—and what it does not
The Wazuh indexer bulk API supports multiple index, create, update, or delete operations in one request, and documents HTTP 400 as a bad-request response. The status classifies the request; by itself, it does not identify why it was rejected. Read the complete response body and correlate its details with indexer logs and the rejected alert. OpenSearch bulk API
#1 Best Overall
- Compact and Efficient Design: The FortiGate 40F is designed for small to mid-sized businesses and enterprise branch offices, featuring a compact, fanless desktop form factor that ensures quiet operation and minimizes space usage.
- Robust Connectivity Options: Equipped with 5 GE RJ45 ports, including 1 WAN port and 4 internal ports, this model provides essential connectivity and flexibility for various network configurations in a small-scale environment.
- High-Performance Security: Offers up to 1 Gbps IPS throughput and 600 Mbps threat protection throughput, using Fortinet’s purpose-built security processor technology to deliver industry-leading performance and protection for SSL encrypted traffic.
- Advanced Threat Protection: Integrated with Fortinet’s AI-powered FortiGuard Labs, the FortiGate 40F offers comprehensive cybersecurity, identifying and mitigating both known and unknown threats to maintain robust security across your network.
- Simplified Management and Deployment: Features a user-friendly management console that provides comprehensive network automation and visibility, coupled with Zero Touch Integration with Fortinet’s Security Fabric for easy deployment.
Look for a named field path, parsing or mapping details, request-format problems, or another specific error. If the response does not identify a mapping problem, do not treat one as established. A 400 is not proof that two alerts gave the same field incompatible shapes.
Test whether a field changes shape
A field-path conflict is plausible when the same path is represented differently across documents—for example, as a nested object in one alert and as a scalar value in another—or when either shape conflicts with a type already present in the index mapping. Mappings define fields and their types, but the source documents and the mapping must be checked against the exact error before choosing a fix. OpenSearch field types
- Find the affected alert. Locate it in
/var/ossec/logs/alerts/alerts.jsonand record its timestamp, alert ID, and structure at the field path named in the error. - Find the matching failure evidence. Check Wazuh server/Filebeat or connector logs and indexer logs around that timestamp. Correlate the rejected request with the alert rather than relying on an unrelated error nearby.
- Read the full bulk response. Identify the specific field, parser, mapping, request-format, or other detail it provides. If it names no field, do not infer a field-shape conflict from the status alone.
- Compare documents and mapping. Compare the rejected alert with an accepted alert at the same path. Inspect the current index mapping and the applicable template to see whether the field’s representation and intended type are consistent. The mapping API covers field types and dynamic-mapping choices. OpenSearch mapping API
- Verify the outcome. After a targeted data-shape or template change, check whether new alerts are accepted and whether they appear through the deployment’s index pattern and dashboard time range.
A Wazuh community discussion describes mapping conflicts in alert and archive indices, but it is supporting context, not evidence that every missing alert or HTTP 400 has the same cause. Wazuh community discussion of mapping conflicts
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- HARDWARE PLUS SECURITY SERVICES: FortiGate-60F Firewall Appliance bundled with 1 year of FortiCare Premium and FortiGuard Unified Threat Protection.
- UNIFIED THREAT PROTECTION (UTP): Secures against advanced online threats with comprehensive web filtering and anti-botnet technologies.
- OPTIMIZED FOR MEDIUM-SIZED BUSINESSES: Tailored for businesses needing robust security without the infrastructure of larger enterprises.
- RELIABLE CUSTOMER SUPPORT: FortiCare Premium ensures high-quality support and service continuity.
- EFFECTIVE PROTECTION: Employs advanced filtering technologies to safeguard against sophisticated threats.
Choose a fix based on the evidence
If the incoming alert has an inconsistent shape
Correct the upstream data so the same field path has a consistent structure, if the response and document comparison establish that this is the problem. Review any parser, rule, or integration that supplies the conflicting values. The right representation depends on the data and the intended use of the field; do not force a shape change solely because the request returned 400.
If a template defines the wrong type
Correct the intended template or mapping for indices created with it, then confirm the effective mapping before relying on it. A template change does not by itself rewrite a mapping already applied to an existing index.
If the existing index already has an incompatible mapping
Wazuh’s mapping guidance warns that mappings already applied to existing data cannot simply be modified in place. For an existing index that needs a different mapping, Wazuh documents creating a new index with the desired mapping and reindexing the old documents. Plan this against the actual index state, retention requirements, and data-preservation process; do not casually delete an index as a workaround. Wazuh indexer indices
Rank #3
- 【Up to 1100 Mbps VPN Speed 】 Hardware-accelerated WireGuard and OpenVPN-DCO deliver up to 1100 Mbps VPN throughput, over 3× faster than Brume 2 for smooth remote access and file transfers.
- 【Three 2.5G Ports & Multi-WAN】Tri-port 2.5GbE design with flexible WAN LAN configuration supports multi-gigabit wired setups, dual-ISP Multi-WAN and failover to keep home and SOHO networks online.
- 【Stealth VPN Obfuscation】VPN obfuscation disguises VPN traffic as regular HTTPS, helping you evade blocking, bypass restrictive networks and maintain stable, private connections.
- 【DPI protection】Deep Packet Inspection with visual dashboards blocks adult/gambling/malicious sites, while SQM and QoS prioritize gaming, calls, and video when bandwidth is tight
- 【OpenWrt & USB 3.0 Expansion】OpenWrt with 1GB DDR4 and 8GB eMMC lets you install plugins and build VPN, ad-blocking or NAS, while USB 3.0 Type‑C connects high-speed storage or 4G/5G dongles
Check connector and queue behavior separately
Wazuh’s connector documentation describes an in-memory queue, retries for selected transient failures, and the possibility of dropped events when the queue overflows. Those details are version- and configuration-dependent; they do not establish that a particular HTTP 400 followed that path. Check the connector behavior and logs for the installed release, along with any available queue evidence, rather than assuming every missing document was dropped in the same way. Wazuh indexer connector README
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsKeep the diagnosis specific to your deployment
Documentation describes the general flow, but the installed Wazuh version, connector configuration, templates, and actual index state determine what happened in a particular deployment. Use the rejected document, complete response, relevant logs, and current mapping together. Only after new alerts are accepted should you check their visibility in the dashboard using the appropriate index pattern and time range.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
