#### Notifications

Notification targets supported by MinIO are in the following list. To configure individual targets please refer to more detailed documentation [here](https://docs.min.io/community/minio-object-store/administration/monitoring.html#bucket-notifications).

```
notify_webhook        publish bucket notifications to webhook endpoints
notify_amqp           publish bucket notifications to AMQP endpoints

        }
        return response.getStatus().getStatus();
    }

    /**
     * Calculates the memory size of a document data map.
     * This is useful for monitoring memory usage during indexing operations.
     *
     * @param dataMap the document data as a map of field names to values
     * @return the estimated memory size in bytes
     */

### 10.2 Fallback to Oplocks
```java
if (!context.getConfig().isUseLeases() || !session.supports(SMB3_0)) {
    // Fall back to traditional oplock mechanism
    useOplockInstead();
}
```

## 11. Monitoring and Metrics

### 11.1 Lease Statistics
```java
public class LeaseStatistics {
    private final AtomicLong leasesRequested = new AtomicLong();
    private final AtomicLong leasesGranted = new AtomicLong();

        }
        
        // Fall back to direct server query
        return directory.performDirectEnumeration();
    }
}
```

## 10. Monitoring and Metrics

### 10.1 Directory Cache Statistics
```java
public class DirectoryCacheStatistics {
    private final AtomicLong cacheHits = new AtomicLong();

    
    // Should work even if RDMA provider is not available
    file.createNewFile();
    assertTrue(file.exists());
}
```

## 8. Performance Monitoring

### 8.1 RDMA Statistics
```java
public class RdmaStatistics {
    private final AtomicLong rdmaReads = new AtomicLong();
    private final AtomicLong rdmaWrites = new AtomicLong();

 * </ul>
 *
 * <p>The updater runs continuously until crawling is finished and all documents are processed.
 * It includes error handling, retry logic, and performance monitoring capabilities.
 *
 */
public class IndexUpdater extends Thread {
    /** Logger for this class */
    private static final Logger logger = LogManager.getLogger(IndexUpdater.class);

                }
            }));
        }
        
        // Wait for all reconnections
        CompletableFuture.allOf(futures.toArray(new CompletableFuture[0])).join();
    }
}
```

## 11. Monitoring and Metrics

### 11.1 Handle Statistics
```java
public class HandleStatistics {
    private final AtomicLong handlesRequested = new AtomicLong();
    private final AtomicLong handlesGranted = new AtomicLong();

import java.util.Map.Entry;
import java.util.concurrent.Executor;
import java.util.concurrent.TimeUnit;
import java.util.concurrent.TimeoutException;
import java.util.logging.Level;

/**
 * A manager for monitoring and controlling a set of {@linkplain Service services}. This class
 * provides methods for {@linkplain #startAsync() starting}, {@linkplain #stopAsync() stopping} and

 *
 * <h4>Frameworks</h4>
 *
 * <p>When chaining together a graph of asynchronous operations, you will often find it easier to
 * use a framework. Frameworks automate the process, often adding features like monitoring,
 * debugging, and cancellation. Examples of frameworks include:
 *
 * <ul>
 *   <li><a href="https://dagger.dev/producers.html">Dagger Producers</a>
 * </ul>
 *

You can use simple tools like `htop` to see the CPU and RAM used in your server or the amount used by each process. Or you can use more complex monitoring tools, which may be distributed across servers, etc.

## Recap { #recap }

You have been reading here some of the main concepts that you would probably need to keep in mind when deciding how to deploy your application: