|
1 | 1 | [[release-notes-header-8.18.0]] |
2 | 2 | == 8.18 |
3 | 3 |
|
| 4 | +[discrete] |
| 5 | +[[release-notes-8.18.3]] |
| 6 | +=== 8.18.3 |
| 7 | + |
| 8 | +[discrete] |
| 9 | +[[enhancements-8.18.3]] |
| 10 | +==== Enhancements |
| 11 | +* Adds `dns` event collection for macOS for {elastic-defend} ({kibana-pull}223566[#223566]). |
| 12 | +* Adds pricing information about Elastic Managed LLM in AI Assistant and Attack Discovery tours and callouts ({kibana-pull}221566[#221566]). |
| 13 | +* Adds local file path support for `xpack.productDocBase.artifactRepositoryUrl` ({kibana-pull}217046[#217046]). |
| 14 | + |
| 15 | +[discrete] |
| 16 | +[[bug-fixes-8.18.3]] |
| 17 | +==== Fixes |
| 18 | +* Fixes a bug where OSS models didn't work when streaming was ON ({kibana-pull}224129[#224129]). |
| 19 | +* Fixes a bug where cell actions didn't work when opening a Timeline from specific rules ({kibana-pull}223302[#223302]). |
| 20 | +* Fixes an issue where the entity risk score feature stopped persisting risk score documents ({kibana-pull}221937[#221937]). |
| 21 | +* Fixes overflow issues with the threat match mapping component when you viewed the rule upgrade flyout on a smaller screen ({kibana-pull}218628[#218628]). |
| 22 | +* Ensures the {bedrock} connector respects the action proxy configuration ({kibana-pull}224130[#224130]). |
| 23 | +* Ensures the OpenAI connector respects the action proxy configuration for all sub-actions ({kibana-pull}219617[#219617]). |
| 24 | + |
4 | 25 | [discrete] |
5 | 26 | [[release-notes-8.18.2]] |
6 | 27 | === 8.18.2 |
@@ -48,6 +69,9 @@ PUT /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipelin |
48 | 69 |
|
49 | 70 | After you complete this step, risk scores should automatically begin to successfully persist during the entity risk engine's next run. Details for the next run time are described on the **Entity risk score** page, where you can also manually run the risk score by clicking **Run Engine**. |
50 | 71 |
|
| 72 | +*Resolved* + |
| 73 | +This issue is fixed in {stack} version 8.18.3. |
| 74 | +
|
51 | 75 | ==== |
52 | 76 | // end::known-issue[] |
53 | 77 |
|
@@ -108,6 +132,9 @@ PUT /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipelin |
108 | 132 |
|
109 | 133 | After you complete this step, risk scores should automatically begin to successfully persist during the entity risk engine's next run. Details for the next run time are described on the **Entity risk score** page, where you can also manually run the risk score by clicking **Run Engine**. |
110 | 134 |
|
| 135 | +*Resolved* + |
| 136 | +This issue is fixed in {stack} version 8.18.3. |
| 137 | +
|
111 | 138 | ==== |
112 | 139 | // end::known-issue[] |
113 | 140 |
|
@@ -189,6 +216,9 @@ PUT /_ingest/pipeline/entity_analytics_create_eventIngest_from_timestamp-pipelin |
189 | 216 |
|
190 | 217 | After you complete this step, risk scores should automatically begin to successfully persist during the entity risk engine's next run. Details for the next run time are described on the **Entity risk score** page, where you can also manually run the risk score by clicking **Run Engine**. |
191 | 218 |
|
| 219 | +*Resolved* + |
| 220 | +This issue is fixed in {stack} version 8.18.3. |
| 221 | +
|
192 | 222 | ==== |
193 | 223 | // end::known-issue[] |
194 | 224 |
|
|
0 commit comments