If the lag detector's logger is set to `DEBUG` then the master will capture the hot threads on the lagging node and report them in its logs. However it's quite possible for this log message to be many kB in size, and log messages are apparently truncated at 10kB by default.

We should find another way to report this information to avoid hitting this size limit. Perhaps simply split the hot threads output up across multiple log messages, or perhaps find a different way to report it.
server/src/main/java/org/elasticsearch/common/ReferenceDocs.java
* for testing, but all items use {@link #VERSION_COMPONENT} ({@code getVersionComponent(Version.CURRENT, Build.CURRENT.isSnapshot())})
     * which relates to the current version and build.
     */
    static String getVersionComponent(Version version, boolean isSnapshot) {
        return isSnapshot && version.revision == 0 ? UNRELEASED_VERSION_COMPONENT : version.major + "." + version.minor;
    }
    @Override
    public String toString() {
        return "https://www.elastic.co/guide/en/elasticsearch/reference/" + VERSION_COMPONENT + "/" + relativePath;
    }
    /**
     * @return a list of links which are expected to exist for a particular version of Elasticsearch, which is either all links (if the docs
     * are released) or no links (otherwise). Exposed for testing the behaviour of different versions, but for the current version use
     * {@link #linksToVerify()}.
     */
    static List<ReferenceDocs> linksToVerify(Version version, boolean isSnapshot) {
        if (version.revision == 0 && isSnapshot == false) {
            return List.of();
        }
        return Arrays.stream(values()).toList();
    }
    /**
     * @return a list of links which are expected to exist for the current version of Elasticsearch, which is either all links (if the docs
     * are released) or no links (otherwise).
     */
    public static List<ReferenceDocs> linksToVerify() {
        return linksToVerify(Version.CURRENT, Build.CURRENT.isSnapshot());
    }
}