+ ", hotThread=" + hotThread + "]";
        }

    }

    /**
     * Initializes OpenSearch monitoring probes.
     * Forces the loading of process, OS, and JVM monitoring probes
     * to ensure they are available for system monitoring during crawling.
     */
    static void initializeProbes() {
        // Force probes to be loaded
        ProcessProbe.getInstance();

     * @return the timeout task for monitoring
     */
    public TimeoutTask startMonitorTask(final JobLog jobLog) {
        final TimeoutTarget target = new MonitorTarget(jobLog);
        return TimeoutManager.getInstance().addTimeoutTarget(target, monitorInterval, true);
    }

    /**
     * Sets the monitor interval for job monitoring.
     *

     * -2: use system default, -1: never expire, 0 or positive: expire after specified days.
     */
    protected int documentExpires = -2;

    /**
     * Hot thread monitoring interval in seconds.
     * -1: disabled, positive value: enable hot thread monitoring with specified interval.
     * Used for performance analysis and debugging of the crawler process.
     */
    protected int hotThreadInterval = -1;

    /**

import org.opensearch.common.unit.TimeValue;

/**
 * Monitor target for tracking hot threads in the OpenSearch cluster.
 * This class extends MonitorTarget to provide monitoring functionality for
 * hot threads, which helps identify performance bottlenecks and resource
 * usage issues in the search engine cluster.
 */
public class HotThreadMonitorTarget extends MonitorTarget {

kibana 7 settings for fess
=====

Providing example of kibana settings file for monitoring search logs of fess.

## Install

1. Install and launch Fess.
1. Install and launch kibana.
1. Go to kibana home [http://localhost:5601/](http://localhost:5601/).
1. Click **Management**.
1. Click **Index Patterns**.
1. Click **Create index pattern** button
1. Input "fess\_log\*" to the textbox of **index pattern**.
1. Click **Next step**.

            // If we get here, the method executed successfully
            assertTrue("expired method executed successfully", true);
        } catch (Throwable t) {
            // In test environments, system monitoring may fail due to missing dependencies
            // or restricted access to system resources. This is acceptable.
            // We primarily want to ensure the method can be called without compilation errors

 * (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>
 *

import org.opensearch.monitor.os.OsProbe;
import org.opensearch.monitor.os.OsStats;
import org.opensearch.monitor.process.ProcessProbe;

/**
 * This class is a timer target for monitoring system-level statistics.
 * It collects and logs information about the operating system, process,
 * JVM, and search engine.
 */
public class SystemMonitorTarget extends MonitorTarget {

  public boolean isFair() {
    return fair;
  }

  /**
   * Returns whether this monitor is occupied by any thread. This method is designed for use in
   * monitoring of the system state, not for synchronization control.
   */
  public boolean isOccupied() {
    return lock.isLocked();
  }

  /**

 * [OkHttp Profiler](https://plugins.jetbrains.com/plugin/11249-okhttp-profiler): An IntelliJ plugin for monitoring OkHttp calls.
 * [OkReplay](https://github.com/airbnb/okreplay): Record and replay OkHttp network interaction in your tests.
 * [okhttp-signpost](https://github.com/pakerfeldt/okhttp-signpost): OAuth signing with signpost and OkHttp.