// Schedule periodic tasks
        schedulePeriodicTasks();
    }
    
    private void schedulePeriodicTasks() {
        // Heartbeat monitoring
        scheduler.scheduleAtFixedRate(this::checkHeartbeats, 30, 30, TimeUnit.SECONDS);
        
        // Registration monitoring
        scheduler.scheduleAtFixedRate(this::monitorRegistrations, 10, 10, TimeUnit.SECONDS);
    }
    

 * It contains various attributes related to the crawler's state, configuration, and runtime data.
 * This class provides methods to access and modify these attributes, allowing for control and monitoring
 * of the crawler's behavior.
 *
 * <p>
 * The context includes information such as the session ID, active thread count, access count, crawler status,

 * (or {@link FluentFuture#transform(com.google.common.base.Function, Executor)
 * FluentFuture.transform}), but 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>
 *

        }
        pb.redirectErrorStream(true);

        Process currentProcess = null;
        MonitorThread mt = null;
        try {
            currentProcess = pb.start();

            // monitoring
            mt = new MonitorThread(currentProcess, executionTimeout);
            mt.start();

# Whether to ignore idle threads in hot thread monitoring.
crawler.hotthread.ignore_idle_threads=true
# Interval for hot thread monitoring (e.g., 500ms).
crawler.hotthread.interval=500ms
# Number of snapshots for hot thread monitoring.
crawler.hotthread.snapshots=10
# Number of threads for hot thread monitoring.
crawler.hotthread.threads=3
# Timeout for hot thread monitoring (e.g., 30s).
crawler.hotthread.timeout=30s

            return "Options [sessionId=" + sessionId + ", name=" + name + ", propertiesPath=" + propertiesPath + "]";
        }
    }

    /**
     * Initializes the necessary probes for monitoring system resources.
     */
    static void initializeProbes() {
        // Force probes to be loaded
        ProcessProbe.getInstance();
        OsProbe.getInstance();
        JvmInfo.jvmInfo();
    }

/**
 * This job is responsible for executing the suggest creator process.
 * It builds and runs a command-line process to generate suggest data,
 * handling classpath setup, system properties, and process monitoring.
 */
public class SuggestJob extends ExecJob {

    private static final Logger logger = LogManager.getLogger(SuggestJob.class);

    /**
     * Constructs a new suggest job.
     */

import org.slf4j.LoggerFactory;

import jcifs.CIFSContext;
import jcifs.dcerpc.DcerpcHandle;

/**
 * Client implementation for the SMB Witness RPC protocol (MS-SWN).
 * Provides communication with witness servers for monitoring SMB resource availability.
 */
public class WitnessRpcClient implements AutoCloseable {
    private static final Logger log = LoggerFactory.getLogger(WitnessRpcClient.class);

    private final InetAddress serverAddress;

 * Tracks all AutoCloseable resources and ensures proper cleanup.
 *
 * Features:
 * - Automatic resource cleanup with weak references
 * - Resource leak detection
 * - Resource usage monitoring
 * - Periodic cleanup of abandoned resources
 * - Detailed resource tracking and reporting
 */
public class ResourceManager {

    private static final Logger log = LoggerFactory.getLogger(ResourceManager.class);

 * (or {@link FluentFuture#transform(com.google.common.base.Function, Executor)
 * FluentFuture.transform}), but 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>
 *