# Warehouse Observability Enhancements


RudderStack's latest warehouse observability enhancements give you detailed insights into why the data going to a [warehouse destination](https://www.rudderstack.com/docs/destinations/warehouse-destinations/) was discarded, especially in cases where there is a data type mismatch and the event data does not conform to the [Warehouse Schema](https://www.rudderstack.com/docs/destinations/warehouse-destinations/warehouse-schema/).

## How the feature works

RudderStack discards any event data going into a [warehouse destination](https://www.rudderstack.com/docs/destinations/warehouse-destinations/) that does not strictly conform to the [Warehouse Schema spec](https://www.rudderstack.com/docs/destinations/warehouse-destinations/warehouse-schema/) and [cannot be fixed](https://www.rudderstack.com/docs/destinations/warehouse-destinations/warehouse-schema/#how-rudderstack-handles-data-type-mismatch). 

In such cases, RudderStack puts the discarded records into a `rudder_discards` table along with a reason. With the latest observability enhancements, the reasons will give more insights on exactly why the data was discarded.

Some examples are shown below:

- `incompatible schema conversion from string to boolean`
- `incompatible schema conversion from string to int`
- `incompatible schema conversion from datetime to string`
- `incompatible schema conversion from bigint to float`