|
| 1 | +version: 8.18.8 |
| 2 | +entries: |
| 3 | + - kind: enhancement |
| 4 | + summary: agent cleans up downloads directory and the new versioned home if upgrade fails |
| 5 | + description: "" |
| 6 | + component: elastic-agent |
| 7 | + pr: |
| 8 | + - https://github.com/elastic/elastic-agent/pull/9386 |
| 9 | + issue: |
| 10 | + - https://github.com/elastic/elastic-agent/issues/5235 |
| 11 | + impact: "" |
| 12 | + action: "" |
| 13 | + timestamp: 1755268130 |
| 14 | + file: |
| 15 | + name: 1755268130-cleanup-downloads-directory-and-the-new-versioned-home-if-upgrade-fails.yaml |
| 16 | + checksum: 5d9cdb7ac38cde4951de2c63368b504161601607 |
| 17 | + - kind: enhancement |
| 18 | + summary: when there is a disk space error during an upgrade, agent responds with clean insufficient disk space error message |
| 19 | + description: "" |
| 20 | + component: elastic-agent |
| 21 | + pr: |
| 22 | + - https://github.com/elastic/elastic-agent/pull/9392 |
| 23 | + issue: |
| 24 | + - https://github.com/elastic/elastic-agent/issues/5235 |
| 25 | + impact: "" |
| 26 | + action: "" |
| 27 | + timestamp: 1757010848 |
| 28 | + file: |
| 29 | + name: 1757010848-agent-responds-with-clean-insufficient-disk-space-error-message.yaml |
| 30 | + checksum: f56341e6c991397a73bc108a1f7b3db04c6a3abc |
| 31 | + - kind: bug-fix |
| 32 | + summary: Include aggregated agent status in HTTP liveness checks |
| 33 | + description: "" |
| 34 | + component: elastic-agent |
| 35 | + pr: |
| 36 | + - https://github.com/elastic/elastic-agent/pull/9673 |
| 37 | + issue: |
| 38 | + - https://github.com/elastic/elastic-agent/issues/9576 |
| 39 | + impact: "" |
| 40 | + action: "" |
| 41 | + timestamp: 1757502748 |
| 42 | + file: |
| 43 | + name: 1757502748-liveness-include-agent-aggregated-status.yaml |
| 44 | + checksum: 7f059a7bc06c911463fcb96cfc0c077d3e1c7d62 |
| 45 | + - kind: bug-fix |
| 46 | + summary: reduce-default-telemetry-frequency |
| 47 | + description: Reduce the default telemetry frequency to 60 seconds. This change aims to lower infrastructure costs and reduce label churn in time-series storage. High-cardinality labels sampled too frequently inflate storage and index size, and increase query latency with limited added value. Environments that require higher resolution can change the `collection_interval` for `hostmetrics`, `kubeletstats` and `k8s_cluster` receivers to a lower value. |
| 48 | + component: elastic-agent |
| 49 | + pr: |
| 50 | + - https://github.com/elastic/elastic-agent/pull/9987 |
| 51 | + issue: [] |
| 52 | + impact: "" |
| 53 | + action: "" |
| 54 | + timestamp: 1758039757 |
| 55 | + file: |
| 56 | + name: 1758039757-reduce-default-telemetry-frequency.yaml |
| 57 | + checksum: b898653d4d803506feb56c9aac563e3615f46ffe |
| 58 | + - kind: bug-fix |
| 59 | + summary: Fix stuck upgrade state by clearing coordinator overridden state after failed upgrade |
| 60 | + description: "" |
| 61 | + component: elastic-agent |
| 62 | + pr: |
| 63 | + - https://github.com/elastic/elastic-agent/pull/9992 |
| 64 | + issue: [] |
| 65 | + impact: "" |
| 66 | + action: "" |
| 67 | + timestamp: 1758045690 |
| 68 | + file: |
| 69 | + name: 1758045690-clear-coordinator-state.yaml |
| 70 | + checksum: f91a0478a6a6a49b3e6e0bb974f3341ca1ce0677 |
| 71 | + - kind: bug-fix |
| 72 | + summary: Include components units status in HTTP liveness checks |
| 73 | + description: "" |
| 74 | + component: elastic-agent |
| 75 | + pr: |
| 76 | + - https://github.com/elastic/elastic-agent/pull/10158 |
| 77 | + - https://github.com/elastic/elastic-agent/pull/10207 |
| 78 | + - https://github.com/elastic/elastic-agent/pull/10264 |
| 79 | + - https://github.com/elastic/elastic-agent/pull/10265 |
| 80 | + - https://github.com/elastic/elastic-agent/pull/10060 |
| 81 | + issue: |
| 82 | + - https://github.com/elastic/elastic-agent/issues/8047 |
| 83 | + impact: "" |
| 84 | + action: "" |
| 85 | + timestamp: 1758287649 |
| 86 | + file: |
| 87 | + name: 1758287649-fix-liveness_units.yaml |
| 88 | + checksum: 56d3167373e1447971495c4d8fc7aacf534b2ab0 |
0 commit comments