Skip to content

Releases: conzetti/elastic-agent-release

v2.0.0

20 Feb 21:56
7e52cb1
Compare
Choose a tag to compare

What's Changed (TL;DR)

  • 🔪 Use native systemd configuration by @conzetti in #7
  • Remote upgrades are now possible via Fleet Server

Full Changelog: v1.0.0...v2.0.0

v1.0.0

02 Feb 21:05
6bfe185
Compare
Choose a tag to compare

TL;DR

  • Includes opinionated tags for deployment & instance name by default
  • Breaking change: changes the parameter names to use underscores over hyphens

v0.0.23-alpha

22 Nov 19:09
84a356a
Compare
Choose a tag to compare

TL;DR

  • Elastic-agents supporting single word tags; adding an ability to add these in a runtime configuration'
  • Added a runtime.yml

Detail
Nodes deployed by BOSH are often hard to identify purely by the hostname that they are registered in Fleet with. Tagging allows us to at least have the understanding of what environment/foundation they belong to (or add tags that are helpful in some other meaningful way).

The README was updated and an example manifest was also updated to provide some guidance on how to apply tags when the elastic-agent enrolls.

v0.0.21-alpha

13 Oct 03:15
2f1d88d
Compare
Choose a tag to compare
v0.0.21-alpha Pre-release
Pre-release

TL;DR

  • First functional release
  • Agent starts / restarts on failure
  • Agent checks-in with defined fleet system
  • Currently only intended to be used as BOSH addon
  • Agent correctly gathers metrics, logs from the BOSH-managed system

Untested

  • Remote upgrades (via Fleet Server)
  • Long-term usage
  • Collocation on TAS/CloudFoundry instances

Detail
This release leverages the separate enroll and run features of the agent, rather than using the install feature to add a systemd unit to the notes. This project may gravitate towards using the install command and allowing systemd to manage the process, but currently a bug in the elastic-agent registration process makes the install command largely unusable without some manual intervention. The separate enroll and run commands allow the elastic-agent.yml configuration to be templated beforehand and placed in the appropriate directory prior to service start.