BREAKING CHANGE: switched to use hapi's latest versions. Requires Node 8.

v5.0.0

5.0.0

5.0.0

Major update

• switched to use hapi's latest versions. Requires Node 8.

v4.0.2

Bug Fixes

• Fixed an issue where attempting to log an object with a circular reference would result in an infinite loop

v4.0.1

Bug Fixes

• Fixed an issue where a tag would not be omitted if it had an empty string (causing the line item to be discarded later).
• Fixed an issue where string values containing newlines were not being properly escaped (causing the line item to be discarded later).

v4.0.0

Good-influx 4.0.0 - Schema-based influx logging

Why the move to schemas?

The problems which I had been consistently running into with the current form of the plugin were around maintaining existing data setups as well as building new ones with data that can be found in different formats but should ultimately be returned as something specific. I was consistently struggling to create setups which maintained what existed before and I was creating a ton of code to ensure that the new measurements I was building were writing logs that conformed to the right types.

Schema-based formatting will allow people to strongly enforce the structure of what they are logging and prevent issues of different events having different data types. It also allows this data to be more discoverable as it will always match one of your schema files. Lastly, with schemas it becomes a very trivial process to add extra data or even whole processing of events.

What breaking changes are there?

I have removed some things which are no longer useful now that you can define a schema.
The things I removed are:

• [metadata] - This was too limiting as it only allowed you to add tags. This has been replaced by defaultFields and defaultTags.
• [customLogFormatters] - This was too limited in scope anyways, but is also now fully unnecessary as schemas take care of this for you.
• [fieldTags] - This became unnecessary as schemas allow you to specify what things to put in tags.
• [measurementOverride] - Replaced by eventName, which now applies before routing the event to a formatter.
• [valueTransformer] - This became unnecessary as schemas fully handle the functionality that this provided.

Wow... that's a lot of things removed... what didn't change then?

The basic line item formats that the plugin was previously providing are still intact. They were just moved to be schemas.

So, what all is new?

There are many new things! The biggest one is that you can structure your data into schemas which creates a very strong typing and formatting for line items as well as a finer control over fields and tags.

Otherwise:

• [defaultTags] and [defaultFields] - These replace the singular metadata config. They allow you to specify things that should be present in tags or fields on all events.
• [eventName] - This replaced the old measurementOverride. It now runs before determining which set of schemas to process, allowing you to choose how an event gets processed based on things besides just its name field. This has no influence on the resultant measurement names, unlike its predecessor.

v3.3.0

New features:

• Flatten data when it is an object (by @barry-dutton-ck)
• Allow field data to be pushed into tags (by @barry-dutton-ck)
• Allow for custom measurement name handling (by @barry-dutton-ck)
• Allow for manipulating the field values before sending them out (by @barry-dutton-ck)

v3.1.0

New features:

• Add measurement prefix (by @ian-harshman-ck)

v3.0.0

Breaking changes:

• Metadata are added as tags only (by @ian-harshman-ck)

v2.3.0

New Features:

• Include Load Data from Ops in Influx Events (by @AlecHFerguson)

v2.2.0

New Features:

• Update line-protocol to include metadata in the tag set (by @sfabriece)