0.2.1

Release v0.2.1

• [Enhancement] - Updated crashplan-ffs-go-pkg to v0.1.0 which adds support for new email FFS fields. (Issue #74)
• [Bug] - Add catch to record on line x: wrong number of fields errors. (Issue #72)

This release requires changes to Elasticsearch Index Template.

0.2.0

Release v0.2.0

• [Enhancement] - Updated oliver elastic to v7.0.8 (Issue #70)
• [Enhancement] - Updated prometheus client_golang to v1.2.1 (Issue #69)
• [Enhancement] - Updated crashplan-ffs-go-pkg to v0.0.9. This adds two new fields: Tab/Window Title and Tab Url. (Issue #68) Note: This change will require index updates if you are using Elasticsearch as a data store

0.1.9

Release v0.1.9

• [Enhancement/Bug] - Rewrote how in progress queries and last completed query are written to disk. This should provide a more accurate record of the state of the application, while reducing bugs with slices changing mid way through. (Issue #59 / Issue #38)
• [Bug] - Fixed handling of POST: 504 Gateway Timeout, these failures should be retried. (Issue #62)
• [Bug] - Fixed issue where retry queries would retry instantly, this would almost always trigger the max queries per minute. Now before the query is retried, it will sleep for the query interval value. (Issue #63)
• [Enhancement] - Increased logstash output timeout to 5 minutes up from 30 seconds. (Issue #64)
• [Bug] - Fixed issue where retry count was not properly incrementing. (Issue #65)

0.1.8

Release v0.1.8

• [Enhancement] - Added support for a semi-Elasticsearch standardized output. This is to be a middle ground between pure FFS format and pure Elasticsearch format. (Issue #58)
• [Enhancement] - Changed how Logstash output works, to be slightly better in handling short connection drops to logstash. (Issue #60)
• [Bug] - Fixed bug when using IP API integration, and events that do not contain public IP Addresses (ie: OneDrive) (Issue #57)
• [Bug] - Fixed bug when using full esStandardized where FFS Exposure value was improperly placed under cloud, instead of being directly under file_event. (Issue #56)

0.1.7

Release v0.1.7

• [Enhancement] - Add a config option called validIpAddressesOnly which makes privateIpAddresses valid. This is needed as currently IPv6 addresses provided by Crashplan FFS are not in a valid form.

0.1.6

Release v0.1.6

• [Bug] - Fixed some issues with the new Elastic standardized output.

0.1.5

Release v0.1.5

• [Enhancement] - Added a new output format called esStandardized. This format matches the standards talked about in https://www.elastic.co/guide/en/beats/devguide/current/event-conventions.html. (Issue #48)
• Important Note: This currently does not have a built in index template, you will need to provide one in Elasticsearch if you want a template.
• [Bug] - Fixed issue where unexpected EOF was not handled. (Issue #45)

0.1.4

Release v0.1.4

This release fixes an versioning issue with v0.1.3.

0.1.3

Release v0.1.3

• [Bug] - Fixed issue where Protocol error was not properly handled. (Issue #39)
• [Bug] - Updated crashplan-ffs-go-pkg to v0.07. This adds support for new FFS fields

IMPORTANT: This release is changes the Elasticsearch index pattern. You may need to reindex you indices.

0.1.2

Release v0.1.2

• [Bug] - Fixed issue where POST: 400 Bad Requests were not properly handled. (Note: This can be kind of weird if you actually provide a bad FFS query, but this needs to be handled as the FFS API can erroneously return this error for some reason) (Issue #33)
• [Bug] - Fixed issue where connection reset by peer errors were not properly retried. This follows the same 10 retries before panicking. (Issue #34)
• [Bug] - Fixed issue where in progress query count for Prometheus metrics was improperly being incremented on retry queries, causing the value to inflate. (Issue #35)