Skip to content

Commit 39a66fa

Browse files
[DOCS] Document a known issue for agentless integrations (#242307)
## Summary This PR documents a known issue that affects the connectivity between agentless integrations and Fleet Server in Elastic Cloud Hosted deployments. Related to elastic/docs-content#3853 Contributes to closing elastic/ingest-docs#1869 --------- Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
1 parent 6328ad5 commit 39a66fa

File tree

1 file changed

+18
-3
lines changed

1 file changed

+18
-3
lines changed

docs/release-notes/known-issues.md

Lines changed: 18 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,21 @@ For Elastic {{observability}} known issues, refer to [Elastic Observability know
88

99
For Elastic Security known issues, refer to [Elastic Security known issues](docs-content://release-notes/elastic-security/known-issues.md).
1010

11+
::::{dropdown} The connection between agentless integrations and {{fleet-server}} is broken
12+
:applies_to: ess: ga
13+
14+
Applies to: {{stack}} <9.1.6
15+
16+
**Details**
17+
18+
When agentless integrations are deployed in {{fleet}} in an {{ech}} deployment, the connection between the agentless integrations and {{fleet-server}} can be broken if the default {{fleet-server}} host URL is modified or if a different host URL is set as the default.
19+
20+
**Resolved**
21+
22+
This issue is resolved in {{stack}} 9.1.6.
23+
24+
::::
25+
1126
::::{dropdown} Alerts aren't generated for rules with alert flapping off and an alert delay higher than 1
1227

1328
Applies to: {{stack}} 9.0.0-9.2.0
@@ -118,10 +133,10 @@ This was resolved in {{stack}} 9.0.3.
118133

119134
Applies to: {{stack}} 9.0.0, 9.0.1, 9.0.2
120135

121-
**Details**
136+
**Details**
122137
Errors occur when rules run during an active maintenance window that has filters and a matching rule category.
123138

124-
**Workaround**
139+
**Workaround**
125140
Remove any filters added to the active maintenance window.
126141

127142
**Resolved**
@@ -167,7 +182,7 @@ Applies to: {{stack}} 9.0.0
167182

168183
**Details**
169184

170-
Rollup indices, like all indices, created in 7.x or earlier need to be reindexed in preparation for migration to 9.0. However, in addition to the normal reindex process the rollup job also needs to be accounted for.
185+
Rollup indices, like all indices, created in 7.x or earlier need to be reindexed in preparation for migration to 9.0. However, in addition to the normal reindex process the rollup job also needs to be accounted for.
171186

172187
**Action**
173188

0 commit comments

Comments
 (0)