Acknowledgements

• I have searched (https://github.com/utmstack/UTMStack/issues) for past instances of this issue
• I have verified that my UTMStack version is up-to-date

Describe the bug

Bitdefender visualizations are referencing outdated Bitdefender field mappings. Because the field names stored in the visualization JSON do not match the current OpenSearch schema, filters and aggregations fail to resolve correctly.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Bitdefender visualizations should continue to work after upgrading to v11.

Current Behavior

• Bitdefender visualizations load, but table values appear as null.
• _source.includes cannot match any fields because the visualization still references old field names.
• Some visualizations return zero documents due to invalid filters.
• Dashboards that depend on Bitdefender data appear empty or partially broken.

Reproduction Steps

1. Go to the Dashboard.
2. Open the Visualization List.
3. Apply a filter for visualizations that use the index pattern v11-log-bitdefender.
4. Click on any Bitdefender visualization.
5. Observe that:
   The visualization loads but shows empty rows or null values.
   Filters and aggregations reference outdated field names.
   The visualization fails to match documents because the v11 mapping uses different field paths.

Possible Solution

No response

Additional Information/Context

No response

UTMStack Version

11.2.3

Operating System and version

Ubuntu

Hypervisor and Version | Server Vendor and Model

Browser and version