Skip to content

[ML][8.18 & 8.19][Bug] Elastic.co : 404 - page not found: Broken links for anomaly detection supplied configurations in 8.18 and 8.19 branches #4023

Closed
7 of 7 issues completed

Description

@LOBrien-EGS

Kibana version:

Elasticsearch version:

Server OS version:

Browser version:
Chrome Version 142.0.7444.176 (Official Build) (arm64)

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug:

Steps to reproduce:

  1. browse to link: https://www.elastic.co/guide/en/machine-learning/8.18/ootb-ml-jobs-siem.html
  2. From table with Titles: Name, Description, Job, Datafeed select "Job" for "auth_high_count_logon_events" row

Expected behavior:
https://www.elastic.co/guide/en/machine-learning/8.17/ootb-ml-jobs-siem.html
Screenshots (if relevant):

Image

Errors in browser console (if relevant):
404 - page not found
The 8.18 branch of kibana does not contain the path
x-pack/plugins/ml/server/models/data_recognizer/modules/security_auth/ml/auth_high_count_logon_events.json.

Provide logs and/or server output (if relevant):

Any additional context:
Works the 8.17 link provided in the "Expected Behavior" section.

Activity

  1. elasticmachine commented on Nov 20, 2025

    @elasticmachine
    Collaborator

    Pinging @elastic/ml-ui (:ml)

  2. changed the title [-]Elastic.co : 404 - page not found The 8.18 branch of kibana does not contain the path on link from elastic.co to github[/-] [+]Elastic.co : 404 - page not found: Broken links for anomaly detection supplied configurations in 8.18 and 8.19 branches[/+] on Nov 20, 2025
  3. changed the title [-]Elastic.co : 404 - page not found: Broken links for anomaly detection supplied configurations in 8.18 and 8.19 branches[/-] [+][ML] Elastic.co : 404 - page not found: Broken links for anomaly detection supplied configurations in 8.18 and 8.19 branches[/+] on Nov 20, 2025
  4. peteharverson commented on Nov 20, 2025

    @peteharverson

    Looks like all the doc links for the anomaly detection supplied configuration job and datafeed configs need updating for the following configs:

    • APM
    • Auditbeat
    • Logs
    • Metricbeat
    • Metrics
    • Security
    • Uptime

    Currently they point at e.g.

    https://github.com/elastic/kibana/blob/8.19/x-pack/plugins/ml/server/models/data_recognizer/modules/security_auth/ml/auth_high_count_logon_events.json
    

    but they need to be in the format

    https://github.com/elastic/kibana/blob/8.19/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_auth/ml/auth_high_count_logon_events.json
    

    by editing x-pack/plugins/ml to x-pack/platform/plugins/shared/ml

  5. nastasha-solomon commented on Nov 20, 2025

    @nastasha-solomon
    Member

    Unfortunately, it appears that links to many of the ML jobs and their datafeeds are broken because the source files were moved to different locations. I went through all of the links on the page and identified broken links in the following sections:

    These links are likely broken in 8.19 as well. ^

    It looks as though the Security anomaly detection configurations page is manually maintained (as opposed to auto-generated), so the next steps are to update the file paths of all the broken references. Using the auth_high_count_logon_events job as an example, the reference to the source file for the job should be updated to:

    https://github.com/elastic/kibana/blob/{branch}/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_auth/ml/auth_high_count_logon_events.json

    And the reference to the job's datafeed should be updated to:

    https://github.com/elastic/kibana/blob/{branch}/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/security_auth/ml/auth_high_count_logon_events.json

  6. nastasha-solomon commented on Nov 20, 2025

    @nastasha-solomon
    Member
  7. added
    Team:ExperienceIssues owned by the Experience Docs Team
    and removed
    needs-teamIssues pending triage by the Docs Team
    on Nov 20, 2025
  8. changed the title [-][ML] Elastic.co : 404 - page not found: Broken links for anomaly detection supplied configurations in 8.18 and 8.19 branches[/-] [+][ML][8.18 & 8.19][Bug] Elastic.co : 404 - page not found: Broken links for anomaly detection supplied configurations in 8.18 and 8.19 branches[/+] on Nov 20, 2025
  9. peteharverson commented on Nov 21, 2025

    @peteharverson

    @nastasha-solomon just to confirm, as well as Security configs you listed here, I think these ones will also need updating for 8.18 and 8.19:

    • APM
    • Auditbeat
    • Logs
    • Metricbeat
    • Metrics
    • Security
    • Uptime

    I'm unsure if the following refs are correct or if they should be pointing to a different page (e.g., docs about data sources for Elasticsearch):
    https://github.com/elastic/stack-docs/blob/da58a8ff6172e901dbed033d049a0f5b824c1b08/docs/en/stack/ml/anomaly-detection/ootb-ml-jobs-siem.asciidoc?plain=1#L27
    https://github.com/elastic/stack-docs/blob/da58a8ff6172e901dbed033d049a0f5b824c1b08/docs/en/stack/ml/anomaly-detection/ootb-ml-jobs-siem.asciidoc?plain=1#L260C122-L260C153

    These links need to open up the manifest.json files, selecting the defautlIndexPattern line of code, in the same way that it works in the latest version of the docs e.g. https://www.elastic.co/docs/reference/machine-learning/ootb-ml-jobs-siem

  10. nastasha-solomon commented on Jan 29, 2026

    @nastasha-solomon
    Member

    Subtasks closed

  11. nastasha-solomon commented on Jan 30, 2026

    @nastasha-solomon
    Member

    Noting for posterity: it appears that elastic/stack-docs#3042 and elastic/stack-docs#3040 fixed the broken links that were mentioned in elastic/stack-docs#3033, elastic/stack-docs#3035, elastic/stack-docs#3037, and elastic/stack-docs#3043. This explains why the PRs for those sub-issues didn't have updates.

    cc: @bmorelli25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Team:ExperienceIssues owned by the Experience Docs TeambugSomething isn't working

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions