Sha256: 999bd6ab88cda04f620e79a7e4334cecbd0fb11b9574d479072831b4fe56822c

Contents?: true

Size: 1.39 KB

Versions: 1

Compression:

Stored size: 1.39 KB

Contents

# fluent-plugin-stdout_ex

Fluentd out\_stdout extension

## Introduction

Although the original `out_stdout` outputs log messages as:

```
2010-05-04 12:02:01 +0900 test: {"test":"test"}
```

this plugin outputs log messages as:

```
2014-05-02 02:02:21 +0900 [info]: 2010-05-04 12:02:01 +0900 test: {"test":"test"}
```

where the first time expresses the current time of *logging*, and the second time expresses the time field of messages, i.e., 
the time when the message is created or, the time written in application logs.

This behavior is very useful because we can see the latency between receiving (logging) and sending (creating) of messages.

## Configuration

```apache
<match **>
  type stdout_ex
</match>
```

## Parameters

Basically same with out\_stdout plugin. See http://docs.fluentd.org/articles/out_stdout

* format ltsv

   The output becomes LTSV format as followings:
    
   current_time:2010-05-04 12:02:01 +0900    time:2010-05-04 12:02:01 +0900    tag:test    record:{"test":"test"}

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new [Pull Request](../../pull/new/master)

## ChangeLog

See [CHANGELOG.md](CHANGELOG.md) for details.

## stdoutright

* Copyright (c) 2014- Naotoshi Seo
* See [LICENSE](LICENSE) for details.

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
fluent-plugin-stdout_ex-0.0.1 README.md