Skip to content

Welcome, user events! Good to have you here!

Compare
Choose a tag to compare
@mountaindude mountaindude released this 22 Apr 06:37
· 810 commits to master since this release
3a745f4

Some good new features in this release, most notably the detailed session start/stop and connection open/close (when users login/logout and open/close apps, respectively) have moved from the Butler project to its new home here in Butler SOS.
That particular feature has a much more natural home in Butler SOS, so this is where it will live from here on.

New features

  1. Added exclude lists for user sessions. If some user accounts (such as system accounts) should not be included in the tracking of user sessions, just add them to the exclude list in the config file. (#62)
  2. Copy user activity tracking ("user events") concept from Butler. That feature belongs to the domain handled by Butler SOS, so it's moved here instead. Future development will happen here rather than in the Butler project. (#147
  3. Added user exclude list to user events config. #151
  4. Added the ability to specify arbitrary tags that is attached to the user event metrics when stored in InfluxDB. #153)
  5. Anonymous telemtry added. The data included in the telemetry data is a) what kinf of computer (Windows/Linux, Node.js version etc) Butler SOS runs on, and b) which features are enabled. That's it - no identifiable data what so ever, and of course no actual metrics. (#148)
  6. Documented the dependency on InfluxDB 1.x, rather than the most recent version 2.x. The latest version is awesome but has some breaking changes which cause it to fail when used with Butler SOS. (#152)

Fixes and patches

  1. Dependencies updated to stay sharp and secure.
  2. Fixed some typos, made some log texts more descriptive. (#149 and more)
  3. Replaced the end-of-life Moment.js library with Luxon.js. (#150)
  4. A bit saner logging in Butler log files when some Sense servers in a cluster were not described in Butler SOS config file. (#155)

Changed behavior and/or breaking changes

  1. The Butler SOS config file has not been very consistent when it comes to using "enable", "enabled" and variants thereof. Confusing. With this version we're cleaning up some of those variants.
    Going forward "enable" is used in Butler SOS (and also in more and more of the other Butler tools. Most of the cases fixed in this release, some remain as todos.
    Using the latest config file syntax is strongly recommended, but efforts have been made to ensure that the old "enabled" variants also work for time being.). (#154)