import org.codelibs.fess.util.ComponentUtil;

/**
 * Pager class for search log pagination and filtering.
 *
 * This class provides pagination functionality for various types of search logs
 * including search logs, click logs, favorite logs, and user information logs.
 * It also supports different aggregation types for analytics and reporting.
 */
public class SearchLogPager implements Serializable {

    /** Serial version UID for serialization. */

    /** Queue for storing search logs. */
    protected Queue<SearchLog> searchLogQueue = new ConcurrentLinkedQueue<>();

    /** Queue for storing click logs. */
    protected Queue<ClickLog> clickLogQueue = new ConcurrentLinkedQueue<>();

    /** Cache for storing user information. */
    protected LoadingCache<String, UserInfo> userInfoCache;

    /** Name of the logger for search logs. */

        }

        /**
         * The total number of logs.
         */
        protected long total = 0;

        /**
         * Sets the list of log entries.
         * @param logs The list of log entries.
         * @return This ApiLogsResponse instance.
         */
        public ApiLogsResponse<T> logs(final List<T> logs) {
            this.logs = logs;
            return this;
        }

        /**

    // GET /api/admin/failureurl/logs
    // PUT /api/admin/failureurl/logs
    /**
     * Retrieves failure URL logs with pagination.
     *
     * @param body the search criteria
     * @return JSON response containing the failure URL logs
     */
    @Execute
    public JsonResponse<ApiResult> logs(final SearchBody body) {
        validateApi(body, messages -> {});

    /**
     * The log type field for filtering search logs.
     */
    public String logType;

    /**
     * The query ID field for searching specific queries.
     */
    public String queryId;

    /**
     * The user session ID field for filtering logs by session.
     */
    public String userSessionId;

    /**
     * The requested time range field for filtering logs by date.
     */

## Log Targets

MinIO supports currently two target types

- console
- http

### Logging Console Target

Console target is on always and cannot be disabled.

### Logging HTTP Target

HTTP target logs to a generic HTTP endpoint in JSON format and is not enabled by default. To enable HTTP target logging you would have to update your MinIO server configuration using `mc admin config set` command.

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

  fi
  if [[ ${error_count} -ge 60 ]] ; then
    echo "Fess is not available."
    cat ${temp_log_file} ./fess-*/logs/*.log
    exit 1
  fi
  sleep 1
done

pushd /tmp >/dev/null
git clone https://github.com/codelibs/fess-testdata.git
popd >/dev/null

cat ${temp_log_file} ./fess-*/logs/*.log
curl -s "http://localhost:9201/_cat/indices?v"

    /**
     * Retrieves crawling info logs with pagination support.
     *
     * @param body the search body containing pagination and filter parameters
     * @return JSON response containing list of crawling info logs
     */
    // GET /api/admin/crawlinginfo/logs
    // PUT /api/admin/crawlinginfo/logs
    @Execute
    public JsonResponse<ApiResult> logs(final SearchBody body) {
        validateApi(body, messages -> {});

import jakarta.annotation.Resource;

/**
 * Service class for managing search logs and related analytics.
 *
 * This service provides functionality for querying, aggregating, and managing
 * various types of search logs including search logs, click logs, favorite logs,
 * and user information logs. It supports different aggregation types for
 * analytics and reporting purposes.
 */
public class SearchLogService {