-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Doc: Add elastic-integration filter tutorial #18229
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.
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
Open
karenzone
wants to merge
5
commits into
elastic:main
Choose a base branch
from
karenzone:ea-tutorial-md
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+183
−1
Open
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7af7d09
Doc: Add elastic-integration filter tutorial
karenzone 9129c56
More content refinement
karenzone 70e1fb3
Add TOC entry and more content cleanup and refinement
karenzone d8d446f
Fix internal and cross-docs links
karenzone 7db4d9b
More content refinement
karenzone File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,22 +1,34 @@ | ||
| # Tutorial: Using the {{ls}} `elastic_integration` filter to extend Elastic {{integrations}} [ea-integrations-tutorial] | ||
|
|
||
| You can use {{ls}} to transform events collected by {{agent}} and paired with an [Elastic integration](integration-docs://reference/index.md). | ||
| --- | ||
| navigation_title: Tutorial to extend Elastic Integrations | ||
| applies_to: | ||
| stack: ga | ||
| serverless: ga | ||
| products: | ||
| - id: elasticsearch | ||
| - id: cloud-hosted | ||
| - id: cloud-enterprise | ||
| - id: cloud-kubernetes | ||
| --- | ||
|
|
||
| # Tutorial: Extend Elastic {{integrations}} with the {{ls}} elastic_integration filter[ea-integrations-tutorial] | ||
|
|
||
| You can use {{ls}} to transform events collected by {{agent}}s and paired with an [Elastic integration](integration-docs://reference/index.md). | ||
|
|
||
| You get the benefits of Elastic integrations--such as the simplicity of ingesting data from a wide variety of data sources and ensuring compliance with the [Elastic Common Schema (ECS)](ecs://reference/index.md)--combined with the extra processing power of {{ls}}. | ||
|
|
||
| This new functionality is made possible by the [`elastic_integration` filter](logstash-docs-md://lsr/plugins-filters-elastic_integration.md) plugin. | ||
| This new functionality is made possible by the [elastic_integration filter](logstash-docs-md://lsr/plugins-filters-elastic_integration.md) plugin. | ||
| When you include the `elastic_integration` filter in your configuration, {{ls}} reads certain field values generated by the {{agent}}, | ||
| and uses them to apply the transformations from Elastic integrations. | ||
| This allows you to further process events in the Logstash pipeline before sending them to their configured destinations. | ||
| This ability allows you to further process events in the Logstash pipeline before sending them to their configured destinations. | ||
|
|
||
| This tutorial walks you through adding the [Crowdstrike integration](integration-docs://reference/crowdstrike-intro.md) sending the data to {{ech}} or self-managed {{es}}. | ||
| This tutorial walks you through adding the [Crowdstrike integration](integration-docs://reference/crowdstrike.md), and sending the data to {{ech}}, {{serverless-full}}, or self-managed {{es}}. | ||
|
|
||
|
|
||
| ## Prerequisites [ea-integrations-prereqs] | ||
|
|
||
| You need: | ||
|
|
||
| * A working {{es}} cluster | ||
| * A working {{ech}} or {{serverless-full}} deployment, or self-managed {{es}} cluster | ||
| * A {{ls}} instance | ||
| * {{fleet-server}} | ||
| * An [{{agent}} installed](docs-content://reference/fleet/install-elastic-agents.md) on the hosts you want to collect data from, and configured to [send output to {{ls}}](docs-content://reference/fleet/logstash-output.md) | ||
|
|
@@ -70,10 +82,9 @@ This policy should be selected by default. | |
|
|
||
| 1. Create a new [{{ls}} pipeline](/reference/creating-logstash-pipeline.md). | ||
| 2. Be sure to include these plugins: | ||
|
|
||
| * [`elastic_agent` input](logstash-docs-md://lsr/plugins-inputs-elastic_agent.md) | ||
| * [`elastic_integration` filter](logstash-docs-md://lsr/plugins-filters-elastic_integration.md) | ||
| * [`elasticsearch` output](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md) | ||
| * [elastic_agent input](logstash-docs-md://lsr/plugins-inputs-elastic_agent.md) | ||
| * [`elastic_integration` filter](logstash-docs-md://lsr/plugins-filters-elastic_integration.md) | ||
| * [`elasticsearch` output](logstash-docs-md://lsr/plugins-outputs-elasticsearch.md) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is nice to include input/output! ❤️ |
||
|
|
||
| Note that every event sent from the {{agent}} to {{ls}} contains specific meta-fields. | ||
| {{ls}} expects events to contain a top-level `data_stream` field with `type`, `dataset`, and `namespace` sub-fields. | ||
|
|
@@ -82,9 +93,9 @@ Note that every event sent from the {{agent}} to {{ls}} contains specific meta-f | |
| {{ls}} frequently synchronizes with {{es}} to ensure that it has the most recent versions of the enabled integrations. | ||
|
|
||
|
|
||
| ### Sample configuration: output to {{ech}} [ea-integrations-ess-sample] | ||
| ### Sample configuration: output to Elastic Cloud [ea-integrations-ech-sample] | ||
|
|
||
| This sample illustrates using the `elastic_agent` input and the `elastic_integration` filter for processing in {{ls}}, and then sending the output to {{ech}}. | ||
| This sample illustrates using the `elastic_agent` input and the `elastic_integration` filter for processing in {{ls}}, and then sending the output to {{ech}} or {{serverless-full}}. | ||
|
|
||
| Check out the [`elastic_integration` filter](logstash-docs-md://lsr/plugins-filters-elastic_integration.md) for the full list of configuration options. | ||
|
|
||
|
|
@@ -109,7 +120,7 @@ output { | |
| } | ||
| ``` | ||
|
|
||
| All processing occurs in {{ls}} before events are forwarded to {{ech}}. | ||
| All processing occurs in {{ls}} before events are forwarded to {{ech}} or {{serverless-full}}. | ||
|
|
||
|
|
||
| ### Sample configuration: output to self-managed {{es}} [ea-integrations-es-sample] | ||
|
|
@@ -141,7 +152,7 @@ output { | |
| } | ||
| ## add elasticsearch | ||
| elasticsearch { | ||
| hosts => "{es-host}:9200" | ||
| hosts => ["{es-host}:9200"] | ||
| user => "elastic" | ||
| password => "changeme" | ||
| ssl_certificate_authorities => "/usr/share/logstash/config/certs/ca-cert.pem" | ||
|
|
||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added references to Serverless throughout as a reminder to see if that's a viable option for this tutorial.