﻿---
title: Custom WMI (Windows Management Instrumentation) Input Package
description: The Custom WMI Input integration is used to ingest data from the Windows Management Instrumentation (WMI) classes. You can use this input to collect instances...
url: https://www.elastic.co/docs/reference/integrations/wmi
---

# Custom WMI (Windows Management Instrumentation) Input Package


|                                                                                                                                     |                                                        |
|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|
| **Version**Version                                                                                                                  | 0.0.1 `product: beta` ([View all](#changelog)View all) |
| **Subscription level**Subscription level[What's this?](https://www.elastic.co/subscriptions)What's this?                            | Basic                                                  |
| **Level of support**Level of support[What's this?](https://www.elastic.co/docs/reference/integrations/level-of-support)What's this? | Elastic                                                |

The Custom WMI Input integration is used to ingest data from the Windows Management Instrumentation (WMI) classes.
You can use this input to collect instances of any WMI class. Please be aware that
when working with WMI queries, it is the user’s responsibility to ensure that queries are safe, efficient, and do not cause unintended side effects. A notorious example of a problematic WMI class is Win32_Product. [Read more in Windows Documentation](https://learn.microsoft.com/en-us/troubleshoot/windows-server/admin-development/windows-installer-reconfigured-all-applications#more-information%5F).

## Requirements

This integration requires Elastic-Agent 8.19.0 or 9.1.0 and above.
This integration is only available on Windows. We refer to the Metricbeat input for the [Compatibility](https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-metricset-windows-wmi#compatibility).

## Configuration

The extensive documentation for the input is currently available [here](https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-metricset-windows-wmi). We highly encourage users to become familiar with the linked documentation.
The most commonly used configuration options are available on the main integration page, while more advanced and customizable options currently resides under the "Advanced options" part of the integration settings page.

### Date Fields Mapping

Elastic-Agent converts WMI properties of type "datetime" to timestamps, but these are serialized as strings in the output. Since date detection is disabled by default, these fields will be stored as strings unless explicitly mapped as dates. To ensure proper mapping, we recommend explicitly setting the mapping in the `@custom` template.
Refer to [this guide](https://www.elastic.co/docs/reference/fleet/data-streams#data-streams-index-templates-edit)
and [this guide](https://www.elastic.co/docs/manage-data/data-store/index-basics#manage-component-templates) for additional
details.

## Changelog

<dropdown title="Changelog">


  | Version        | Details                                                                                                                                      | Kibana version(s) |
  |----------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
  | **0.0.1**0.0.1 | **Enhancement**Enhancement ([View pull request](https://github.com/elastic/integrations/pull/12654)View pull request)WMI Input Package draft |                   |
</dropdown>
