docs: fix broken and redirected links from link checker report - #2661
Open
eschabell wants to merge 1 commit into
Open
docs: fix broken and redirected links from link checker report#2661eschabell wants to merge 1 commit into
eschabell wants to merge 1 commit into
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (13)
🚧 Files skipped from review as they are similar to previous changes (10)
📝 WalkthroughWalkthroughThe workflow now accepts status code 999. Documentation links across project, development, and pipeline pages were updated. An obsolete AWS timer hyperlink was removed. ChangesDocumentation and link-check updates
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pipeline/filters/tensorflow.md`:
- Line 9: Update the Tensorflow Lite description to hyphenate “open-source” when
it modifies “deep learning framework,” without changing the surrounding wording.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: e7110596-2342-419d-b767-b2d71e4e2043
📒 Files selected for processing (13)
.github/workflows/linkcheck.yamlCONTRIBUTING.mdMAINTAINERS.mdREADME.mddevelopment/external-libraries.mddevelopment/wasm-filter-plugins.mdpipeline/filters/tensorflow.mdpipeline/outputs/azure_kusto.mdpipeline/outputs/bigquery.mdpipeline/outputs/chronicle.mdpipeline/outputs/forward.mdpipeline/outputs/influxdb.mdpipeline/outputs/s3.md
eschabell
force-pushed
the
erics_linkchecker_report_fixes
branch
from
August 5, 2026 14:39
2d0bf11 to
92e406a
Compare
Contributor
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
eschabell
force-pushed
the
erics_linkchecker_report_fixes
branch
from
August 5, 2026 14:49
92e406a to
80d2736
Compare
Collaborator
Author
|
@patrick-stephens ready for review! |
eschabell
force-pushed
the
erics_linkchecker_report_fixes
branch
from
August 5, 2026 15:40
80d2736 to
95c640a
Compare
Contributor
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pipeline/outputs/azure_kusto.md`:
- Line 7: Update the Eventhouse link in the Kusto output plugin documentation to
use the canonical Microsoft Learn Eventhouse overview at
learn.microsoft.com/en-us/fabric/real-time-intelligence/eventhouse, while
preserving the surrounding description and other links.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 224df8ae-533e-4abd-8fe1-3fc90437936f
📒 Files selected for processing (13)
.github/workflows/linkcheck.yamlCONTRIBUTING.mdMAINTAINERS.mdREADME.mddevelopment/external-libraries.mddevelopment/wasm-filter-plugins.mdpipeline/filters/tensorflow.mdpipeline/outputs/azure_kusto.mdpipeline/outputs/bigquery.mdpipeline/outputs/chronicle.mdpipeline/outputs/forward.mdpipeline/outputs/influxdb.mdpipeline/outputs/s3.md
🚧 Files skipped from review as they are similar to previous changes (10)
- CONTRIBUTING.md
- pipeline/outputs/forward.md
- pipeline/outputs/bigquery.md
- pipeline/outputs/s3.md
- pipeline/outputs/chronicle.md
- MAINTAINERS.md
- development/external-libraries.md
- pipeline/outputs/influxdb.md
- .github/workflows/linkcheck.yaml
- development/wasm-filter-plugins.md
The monthly link checker reported 3 errors, 1 timeout, and 27 redirects.
Fix the two genuine 404s, correct a citation that silently redirected to
the wrong API, resolve the redirects worth resolving, and stop LinkedIn
from generating a false error every month.
Broken links (404):
- pipeline/outputs/azure_kusto.md: repoint "Authorize the app in your
database" at learn.microsoft.com/en-us/kusto/management/reference-
security-principals. The old URL 404s, and Microsoft's own redirect
from it lands on another 404. The new page carries the
aadapp=ApplicationId;TenantId syntax the step refers to. Also fixed
broken Eventhouse link.
- pipeline/outputs/s3.md: drop the link on the `timer` callback. It
pointed at the AWS IoT Events Data API Timer data type, which is
unrelated to S3 or to Fluent Bit. The S3 upload timer is the internal
cb_s3_upload scheduler callback and has no external documentation, so
there is no correct replacement URL. Keep `timer` as inline code.
Stale citation (redirected to unrelated content):
- pipeline/outputs/bigquery.md: the data deduplication and template
tables bullets cited the legacy streaming page, which Google now
redirects to the Storage Write API. That page documents neither
insertId nor templateSuffix. Cite the tabledata.insertAll REST
reference instead, which documents both.
Redirects resolved:
- CONTRIBUTING.md: vale.sh/docs to docs.vale.sh, drop the trailing slash
on docs.fluentbit.io/manual, and update the Microsoft smart quotes
support URL.
- MAINTAINERS.md: telemetryforge.io to www.telemetryforge.io, and
re-pad the table cell so the pipe alignment still holds.
- README.md: drop the trailing slash on the LinkedIn profile URL.
- development/external-libraries.md, development/wasm-filter-plugins.md:
wasm-micro-runtime moved out of the bytecodealliance org to its own.
The project is still a Bytecode Alliance project, so only the URL
changes.
- pipeline/filters/tensorflow.md: ai.google.dev/edge/litert to
developers.google.com/edge/litert (2 links).
- pipeline/outputs/bigquery.md, pipeline/outputs/chronicle.md:
cloud.google.com to docs.cloud.google.com.
- pipeline/outputs/forward.md: fluentd.org to www.fluentd.org (3 links).
- pipeline/outputs/influxdb.md: add the trailing slash on the InfluxDB
product URL.
- pipeline/outputs/azure_kusto.md: update moved Eventhouse blog link.
Link checker configuration:
- .github/workflows/linkcheck.yaml: accept HTTP 999. LinkedIn returns it
to non-browser clients, so the README profile link is reported as an
error every run even though it resolves fine. Accepting 999 is
narrower than excluding linkedin.com and keeps the URL checked for
DNS and host failures.
Deliberately unchanged: the asciinema link in pipeline/inputs/http.md,
which timed out in CI but resolves normally; the Dynatrace shortlink,
where expanding it to the resolved deep path would be more fragile; the
three fluent-bit issue template links, which only redirect because the
checker is unauthenticated; and the RFC Editor, GitHub codeload, Datadog,
Treasure Data, Docker, and ECR redirects, which are correct as written.
Fixes fluent#2652
Signed-off-by: Eric D. Schabell <eric@schabell.org>
eschabell
force-pushed
the
erics_linkchecker_report_fixes
branch
from
August 5, 2026 19:21
95c640a to
d3a7139
Compare
Collaborator
Author
|
@patrick-stephens ready for review! |
Contributor
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The monthly link checker reported 3 errors, 1 timeout, and 27 redirects.
Fix the two genuine 404s, correct a citation that silently redirected to
the wrong API, resolve the redirects worth resolving, and stop LinkedIn
from generating a false error every month.
Broken links (404):
timercallback. It pointed at the AWS IoT Events Data API Timer data type, which is unrelated to S3 or to Fluent Bit. The S3 upload timer is the internal cb_s3_upload scheduler callback and has no external documentation, so there is no correct replacement URL. Keeptimeras inline code.Stale citation (redirected to unrelated content):
Redirects resolved:
Link checker configuration:
Deliberately unchanged: the asciinema link in pipeline/inputs/http.md,
which timed out in CI but resolves normally; the Dynatrace shortlink,
where expanding it to the resolved deep path would be more fragile; the
three fluent-bit issue template links, which only redirect because the
checker is unauthenticated; and the RFC Editor, GitHub codeload, Datadog,
Treasure Data, Docker, and ECR redirects, which are correct as written.
Fixes #2652
Summary by CodeRabbit
Documentation
Chores