Skip to content

Commit b79810b

Browse files
committed
Alert rule template as asset type
1 parent c6ae9c0 commit b79810b

File tree

1 file changed

+9
-17
lines changed

1 file changed

+9
-17
lines changed

reference/fleet/manage-integrations.md

Lines changed: 9 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -9,29 +9,26 @@ products:
99

1010
# Manage {{agent}} integrations [integrations]
1111

12-
13-
::::{admonition}
14-
Integrations are available for a wide array of popular services and platforms. To see the full list of available integrations, go to the **Integrations** page in {{kib}}, or visit [Elastic Integrations](integration-docs://reference/index.md).
15-
1612
{{agent}} integrations provide a simple, unified way to collect data from popular apps and services, and protect systems from security threats.
13+
Integrations are available for a wide array of popular services and platforms. To see the full list, go to the **Integrations** page in {{kib}}, or visit [Elastic Integrations](integration-docs://reference/index.md).
1714

18-
Each integration comes prepackaged with assets that support all of your observability needs:
15+
Each integration comes prepackaged with assets that support your observability needs:
1916

2017
* Data ingestion, storage, and transformation rules
2118
* Configuration options
19+
* Alert templates to enable users to quickly set up custom alerting rules (available in some integrations) {applies_to}`stack: ga 9.2`
2220
* Pre-built, custom dashboards and visualizations
2321
* Documentation
2422

25-
::::
26-
23+
Note that the **Integrations** app in {{kib}} needs access to the public {{package-registry}} to discover integrations. If your deployment has network restrictions, you can [deploy your own self-managed {{package-registry}}](/reference/fleet/air-gapped.md#air-gapped-diy-epr).
2724

2825
::::{note}
29-
Be aware that some integrations may function differently across different spaces. Also, some might only work in the default space. We recommend reviewing the specific integration documentation for any space-related considerations.
30-
26+
Some integrations may function differently across different spaces, with some working only in the default space. Review the documentation specific to your integration for any space-related considerations.
3127
::::
3228

29+
## Work with integrations [work-with-integrations]
3330

34-
The following table shows the main actions you can perform in the **Integrations** app in {{kib}}. You can perform some of these actions from other places in {{kib}}, too.
31+
You can perform a variety of actions in the **Integrations** app in {{kib}}. Some of these actions are also available from other places in {{kib}}.
3532

3633
| User action | Result |
3734
| --- | --- |
@@ -42,11 +39,6 @@ The following table shows the main actions you can perform in the **Integrations
4239
| [View integration assets](/reference/fleet/view-integration-assets.md) | View the {{kib}} assets installed for a specific integration. |
4340
| [Upgrade an integration](/reference/fleet/upgrade-integration.md) | Upgrade an integration to the latest version. |
4441

45-
::::{note}
46-
The **Integrations** app in {{kib}} needs access to the public {{package-registry}} to discover integrations. If your deployment has network restrictions, you can [deploy your own self-managed {{package-registry}}](/reference/fleet/air-gapped.md#air-gapped-diy-epr).
47-
48-
::::
42+
## Customize integrations [customize-integrations]
4943

50-
:::{tip}
51-
Once you've started using integrations to ingest data, you can customize how that data is managed over time. Refer to [Index lifecycle management](/reference/fleet/data-streams.md#data-streams-ilm) to learn more.
52-
:::
44+
After you've started using integrations to ingest data, you can customize how the data is managed over time. Refer to [Index lifecycle management](/reference/fleet/data-streams.md#data-streams-ilm) to learn more.

0 commit comments

Comments
 (0)