|
| 1 | +version: 8.7.0 |
| 2 | +entries: |
| 3 | + - kind: feature |
| 4 | + summary: Add Entity Analytics input mapping to the Filebeat spec. |
| 5 | + description: "" |
| 6 | + component: spec |
| 7 | + pr: |
| 8 | + - https://github.com/elastic/elastic-agent/pull/2196 |
| 9 | + issue: [] |
| 10 | + timestamp: 1674757194 |
| 11 | + file: |
| 12 | + name: 1674757194-entity-analytics-input.yaml |
| 13 | + checksum: a4f19569e40a0c985eeddea10f3d6841be2f9b17 |
| 14 | + - kind: feature |
| 15 | + summary: Add diagnostics action handler. |
| 16 | + description: | |
| 17 | + Add support for the REQUEST_DIAGNOSTICS action. |
| 18 | + When this action is recieved the agent will collect a diagnostics bundle and |
| 19 | + upload it to fleet-server using the file upload APIs. |
| 20 | + The handler has a configurable rate limit in order to prevent DoS attacks. |
| 21 | + The uploader may retry failures with a configurable exponential backoff. |
| 22 | + component: diagnostics |
| 23 | + pr: |
| 24 | + - https://github.com/elastic/elastic-agent/pull/1703 |
| 25 | + issue: |
| 26 | + - https://github.com/elastic/elastic-agent/issues/1883 |
| 27 | + timestamp: 1674785407 |
| 28 | + file: |
| 29 | + name: 1674785407-add-diagnostics-action-handler.yaml |
| 30 | + checksum: 73538c1e4e9a60b6a99c84eeaa496ed19f46c957 |
| 31 | + - kind: enhancement |
| 32 | + summary: Enhance agent monitoring config to support filebeat /inputs endpoint |
| 33 | + description: "" |
| 34 | + component: monitoring |
| 35 | + pr: |
| 36 | + - https://github.com/elastic/elastic-agent/pull/2171 |
| 37 | + issue: |
| 38 | + - https://github.com/elastic/beats/issues/33953 |
| 39 | + timestamp: 1674822835 |
| 40 | + file: |
| 41 | + name: 1674822835-Enhance-agent-monitoring-config-to-support-filebeat-inputs-endpoint.yaml |
| 42 | + checksum: 62181801e66756a8bff898e8ccf7725acf46cef9 |
| 43 | + - kind: bug-fix |
| 44 | + summary: Correctly migrate unencrypted Fleet configuration when upgrading from versions prior to 8.3. |
| 45 | + description: This is a regression in 8.6 releases only. This works as expected in prior releases. |
| 46 | + component: agent |
| 47 | + pr: |
| 48 | + - https://github.com/elastic/elastic-agent/pull/2256 |
| 49 | + issue: |
| 50 | + - https://github.com/elastic/elastic-agent/issues/2249 |
| 51 | + timestamp: 1676358802 |
| 52 | + file: |
| 53 | + name: 1676358802-migrate-unencrypted-config.yaml |
| 54 | + checksum: a8b5ae705574e19ba2b011b2705e77345622d43e |
| 55 | + - kind: bug-fix |
| 56 | + summary: Restore support for memcached/metrics inputs. |
| 57 | + description: "" |
| 58 | + component: Elastic agent. |
| 59 | + pr: |
| 60 | + - https://github.com/elastic/elastic-agent/pull/2298 |
| 61 | + issue: |
| 62 | + - https://github.com/elastic/elastic-agent/issues/2293 |
| 63 | + timestamp: 1677000534 |
| 64 | + file: |
| 65 | + name: 1677000534-Restore-support-for-memcached-metrics-inputs.yaml |
| 66 | + checksum: a7f53423f9d41a6258437dc969f39a69ace6bf6a |
| 67 | + - kind: unknown |
| 68 | + summary: Render agent config when running leastic-agent inspect --variables-wait |
| 69 | + description: "" |
| 70 | + component: agent |
| 71 | + pr: |
| 72 | + - https://github.com/elastic/elastic-agent/pull/2297 |
| 73 | + issue: |
| 74 | + - https://github.com/elastic/elastic-agent/issues/2206 |
| 75 | + timestamp: 1677048898 |
| 76 | + file: |
| 77 | + name: 1677048898-render-config-for-inspect-with-variable-wait.yaml |
| 78 | + checksum: e097943a4e3a1f6b546d942f842d8e7985b633b0 |
| 79 | + - kind: bug-fix |
| 80 | + summary: Fixes the log message being emitted by the Upgrade Watcher when it detects a crash. |
| 81 | + description: "" |
| 82 | + component: agent |
| 83 | + pr: |
| 84 | + - https://github.com/elastic/elastic-agent/pull/2320 |
| 85 | + issue: [] |
| 86 | + timestamp: 1677255543 |
| 87 | + file: |
| 88 | + name: 1677255543-upgrade-watcher-fix-log.yaml |
| 89 | + checksum: 92674250f10b32d7912621e2483ae5a385016d13 |
| 90 | + - kind: bug-fix |
| 91 | + summary: Fix the first checkin incorrectly reporting the agent as unhealthy. |
| 92 | + description: The agent would sometimes report its intial state as "starting" which was incorrectly translated to "degraded". |
| 93 | + component: agent |
| 94 | + pr: |
| 95 | + - https://github.com/elastic/elastic-agent/pull/2325 |
| 96 | + issue: |
| 97 | + - https://github.com/elastic/elastic-agent/issues/2272 |
| 98 | + timestamp: 1677572502 |
| 99 | + file: |
| 100 | + name: 1677572502-add-fleet-checkin-starting-state.yaml |
| 101 | + checksum: a8fe1b316d5bafaf3deb5788d6f20a2522c2cc67 |
| 102 | + - kind: bug-fix |
| 103 | + summary: Fixes the permissions of the `state/data/tmp` and `state/data/logs` folders when they're setup as part of running `elastic-agent container`. |
| 104 | + description: "" |
| 105 | + component: agent |
| 106 | + pr: |
| 107 | + - https://github.com/elastic/elastic-agent/pull/2330 |
| 108 | + issue: |
| 109 | + - https://github.com/elastic/elastic-agent/issues/2315 |
| 110 | + timestamp: 1677599609 |
| 111 | + file: |
| 112 | + name: 1677599609-fix-container-state-dirs-perms.yaml |
| 113 | + checksum: ecd339cf2ab8cb4b98a0cf5670fb9349d0309b45 |
| 114 | + - kind: bug-fix |
| 115 | + summary: Periodically check for scheduled actions. |
| 116 | + description: Add a timer that will periodically run the action handling mechanism that managed agents use to force it to run scheduled actions. This will allow the agent to handle previously scheduled actions if theres is no communication with fleet, or a checkin does not return any actions. |
| 117 | + component: managed-agent |
| 118 | + pr: |
| 119 | + - https://github.com/elastic/elastic-agent/pull/2344 |
| 120 | + issue: |
| 121 | + - https://github.com/elastic/elastic-agent/issues/2343 |
| 122 | + timestamp: 1677797191 |
| 123 | + file: |
| 124 | + name: 1677797191-dispatch-periodic-flush.yaml |
| 125 | + checksum: 57d2b0f7fac494064d11ea6fbfec1a5e612ceb5b |
| 126 | + - kind: bug-fix |
| 127 | + summary: Fixes for agent not starting to monitor new Kubernetes pods until it is restarted. |
| 128 | + description: | |
| 129 | + Modifies synchronization and debounce mechanism in controller. Notification is not |
| 130 | + blocking anymore so lock holded while notification is being performed can be released and |
| 131 | + other event processed faster. |
| 132 | + component: "" |
| 133 | + pr: |
| 134 | + - https://github.com/elastic/elastic-agent/pull/2349 |
| 135 | + issue: |
| 136 | + - https://github.com/elastic/elastic-agent/issues/2269 |
| 137 | + timestamp: 1678178226 |
| 138 | + file: |
| 139 | + name: 1678178226-Reduced-deadlocks-in-controller.yaml |
| 140 | + checksum: 36c54bf2bad642fea7c64704cc29c77b51116d90 |
| 141 | + - kind: bug-fix |
| 142 | + summary: Fix several possible deadlocks on shutdown. |
| 143 | + description: Fix a deadlock when the agent tries to bind to a port that is already in use. Do not wait for providers to shutdown before exiting. |
| 144 | + component: coordinator |
| 145 | + pr: |
| 146 | + - https://github.com/elastic/elastic-agent/pull/2352 |
| 147 | + issue: |
| 148 | + - https://github.com/elastic/elastic-agent/issues/2310 |
| 149 | + timestamp: 1678471725 |
| 150 | + file: |
| 151 | + name: 1678471725-coordinator_deadlock_fix.yaml |
| 152 | + checksum: 8a6f5498679d1e0f92571e10598130fb63012da8 |
| 153 | + - kind: bug-fix |
| 154 | + summary: Fix permission issue on MacOS Ventura and above when enrolling as part of the installation. |
| 155 | + description: "" |
| 156 | + component: agent |
| 157 | + pr: |
| 158 | + - https://github.com/elastic/elastic-agent/pull/2314 |
| 159 | + issue: |
| 160 | + - https://github.com/elastic/elastic-agent/issues/2103 |
| 161 | + timestamp: 1678553750 |
| 162 | + file: |
| 163 | + name: 1678553750-ventura-permission-issue.yaml |
| 164 | + checksum: f5444bb9940277aea7038f0749b72a32152f6a22 |
0 commit comments