Releases: BenB196/crashplan-ffs-puller
Releases · BenB196/crashplan-ffs-puller
0.1.1
Release v0.1.1
- [Bug] - Made it possible for the app to recover from INTERNAL_STREAM errors. (Issue #21)
- [Bug] - Made it possible for the app to recover from 500 Internal Server errors. (Issue #30)
- [Bug] - Fixed issue when using logstash output which did not properly handle output location validation. (Issue #31)
0.1.0
Release v0.1.0
- [Enhancement] - Added support for Logstash Integration. (Issue #28)
- [Bug] - Updated crashplan-ffs-go-pkg to v0.0.6 to fix a bug with how string slices were being build. (BenB196/crashplan-ffs-go-pkg#8)
- [Misc] - Updated google/go-cmp to v0.3.1
0.0.9
Release v0.0.9
- [Enhancement] - Allow for use of custom index templates with Elasticsearch instead of using the built in index pattern. This should allow for better usability. (Issue #23)
- [Bug] - Fixed issue where the Prometheus metric for in progress queries could become negative. (Issue #26)
0.0.8
Release v0.0.8
- [Bug] - Actually fix issue with waitgroup errors. (Issue #16)
0.0.7
Release v0.0.7
- [Bug] - Fixed issue where program could crash because of missing waitgroup additions. (Issue #16)
- [Bug] - Fixed issue where program would not start if inProgressQueries or lastCompletedQueries file was completely empty. (Issue #22)
0.0.6
Release v0.0.6
- [Feature] - Add support for Elasticsearch indexing by insertionTimestamp and eventTimestamp. (Issue #17)
- [Enhancement] - Add support for enabling best_compression codec on Elasticsearch index compression
- [Enhancement] - Add support for setting refresh_interval on Elasticsearch index
0.0.5
Release v0.0.5
- [Bug] - Fixed issue with poor WaitGroup logic which could cause panics. (Issue #14)
0.0.4
Release v0.0.4
- [Bug] - Updated crashplan-ffs-go-pkg to v0.0.5. This fixes a bug where null fileSizes and removableMediaCapacity were improperly marshaled to 0, instead of being left out. (Issue #12)
0.0.3
Release v0.0.3
- [Bug] - Empty times were being set to 0001-01-01T00:00:00Z instead of being nil. Fixed issue by updating crashplan-ffs-go-pkg to v0.0.4. (Issue #10)
0.0.2
Release of v0.0.2
- [Enhancement] - Allow for the mounting of a trusted root CA in the event that the Elasticsearch cluster being used is using TLS/SSL. (Issue #1)
- [Enhancement] - Updated crashplan-ffs-pkg to v0.0.3, adding support for additional empty fields, and array fileOwners (Issue #6)
- [Bug] - Fixed panic on IP-API integration when the publicIpAddress field of an event was empty. (Issue #4)
- [Bug] - Fixed issue with Elasticsearch integration when using https Elasticsearch, this added support for enabling/disabling sniffing (Issue #5)
- [Bug] - Fixed Elasticsearch mapping breaking with empty Geopoint values. (Issue #8)
Breaking Change:
- Removed support for the protocol configuration value for Elasticsearch Integration. This was not actually needed. (Issue #7)