Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Releases: ViaQ/fluent-plugin-viaq_data_model

add support for .audit prefixed logs

04 Nov 14:54
Compare
Choose a tag to compare

add support for .audit prefixed logs

Only set pipeline_metadata ipaddr6 if specified

06 Aug 22:18
Compare
Choose a tag to compare

Instead of always setting ipaddr6, only set if requested.

release 0.0.19

18 Jul 15:31
Compare
Choose a tag to compare

Fix Bug 1726639. Removing setting log level based on stream
This plugin will no longer set the level field from container log records. The previous method using the stream values stdout and stderr was not correct. Users may set level before calling this plugin and the plugin will honor that setting.

Add support for the systemd.t fields LINE_BREAK STREAM_ID SYSTEMD_INVOCATION_ID

support fluentd 1.x and fluentd 0.12

20 Sep 23:39
14857fd
Compare
Choose a tag to compare

support fluentd 1.x and fluentd 0.12

support fluentd 1.x

20 Sep 22:43
3b34f58
Compare
Choose a tag to compare

support fluentd 1.x

add support for system containers - docker.container_ fields

20 Sep 21:18
Compare
Choose a tag to compare

add support for system containers - docker.container_ fields

Bug 1588772 - After upgrade to 3.6 some logs are not showing in the Kibana

07 Jun 23:51
Compare
Choose a tag to compare

https://bugzilla.redhat.com/show_bug.cgi?id=1588772

Cause: The incoming data has a field record["event"] that
is a String value and not the Hash value expected by the
transform_eventrouter code.

Consequence: This causes the code to throw an error and fluentd
to emit an error like this:

error_class=NoMethodError error="undefined method `key?' for \"request\":String"

Fix: The transform_eventrouter code has been changed to only
process the record["event"] field if it is a Hash.

Result: Records can flow through to the destination again.

bug 1494612. Orphan records missing namespace_name and/or namespace_id

13 Dec 21:38
Compare
Choose a tag to compare

bug 1494612. Orphan records missing namespace_name and/or namespace_id

Bug 1514110 - Aggregated Logging replacing all log levels with '3' and '6' after upgrade to 3.5 from 3.4

20 Nov 19:20
Compare
Choose a tag to compare

https://bugzilla.redhat.com/show_bug.cgi?id=1514110
If there is already a level field in the record, then see if it is
a "close" match to one of the canonical level field values at
https://github.com/ViaQ/elasticsearch-templates/blob/master/namespaces/_default_.yml#L63
e.g. if level is "CRITICAL", convert to "crit", if level
is "WARN" convert to 'warning', etc.

Otherwise, if we cannot use it directly or normalize it, convert
it to its string representation (ruby to_s method) and store
the string value in the level field.

This commit cleans up other level processing and adds several tests
for level processing.

add test for operations namespace to .operations index

26 Sep 13:33
Compare
Choose a tag to compare

add test for operations namespace to .operations index