*
 * This interface defines the contract for search log event objects that can be
 * written to log files or stored in the search index. Implementations include
 * search logs, click logs, favorite logs, and user information logs.
 */
public interface SearchLogEvent {
    /**
     * Gets the unique identifier for this search log event.
     *
     * @return The event ID
     */
    String getId();

    /**

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

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

            cb.specify().doColumn("searchField.*");
        }, this::indexFromSearchLog);
    }

    /**
     * Indexes suggest data from a list of search logs.
     *
     * @param searchLogList The list of search logs to index.
     */
    public void indexFromSearchLog(final List<SearchLog> searchLogList) {
        final Map<String, LocalDateTime> duplicateSessionMap = new HashMap<>();

```sh
docker stop <container_id>
```

### MinIO container logs

To access MinIO logs, you can use the [`docker logs`](https://docs.docker.com/engine/reference/commandline/logs/) command.

```sh
docker logs <container_id>
```

### Monitor MinIO Docker Container

    // 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 -> {});

REM The path to the heap dump location, note directory must exists and have enough
REM space for a full heap dump.
REM FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -XX:HeapDumpPath=%FESS_HOME%/logs/heapdump.hprof

REM Disables explicit GC
set FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -XX:+DisableExplicitGC

REM Ensure UTF-8 encoding by default (e.g. filenames)
set FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -Dfile.encoding=UTF-8

    /** 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;
        }

        /**

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