Skip to content

Doc: Fix link format for proper rendering #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 20, 2024
Merged

Doc: Fix link format for proper rendering #204

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2e2315c
Doc: Fix link format for proper rendering
karenzone Nov 19, 2024
09a7157
Remove literal
karenzone Nov 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...rless/pages/ingest-your-data-ingest-data-through-integrations-logstash.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ such as data routed to multiple destinations or when you need to make your data
{ls} is a powerful, versatile ETL (Extract, Transform, Load) engine that can play an important role in organizations of all sizes.
Some capabilities and features for large, self-managed users aren't appropriate for {serverless-short}.
You'll use the {ls} {logstash-ref}/plugins-outputs-elasticsearch.html[`((es)) output plugin`] to send data to {es3}.
You'll use the {ls} {logstash-ref}/plugins-outputs-elasticsearch.html[{es} output plugin] to send data to {es3}.
Some differences to note between {es3} and self-managed {es}:
* Your logstash-output-elasticsearch configuration uses **API keys** to access {es} from {ls}.
Expand Down