Hi, I'm writing an S3 output plugin for heka. As I am new to golang and
heka, I'm not too sure what's the best way to go about writing the plugin.
Hence I wish to seek you guys' help to resolve some issues that are
plaguing my code.
heka-s3 plugin code: https://github.com/uohzxela/heka-s3/blob/mas
You may want to take a look at
https://github.com/mozilla-services/data-pipeline/blob/master/heka/plugins/s3splitfile/s3splitfile_output.go
Trink
On Wed, May 13, 2015 at 3:42 AM, Alex Jiao wrote:
> Hi, I'm writing an S3 output plugin for heka. As I am new to golang and
> heka, I'm not too sure
Could you post your config file for heka .toml? What is the value for
ticker_interval?
On Wed, May 13, 2015 at 12:42 PM, Alex Jiao wrote:
> Hi, I'm writing an S3 output plugin for heka. As I am new to golang and
> heka, I'm not too sure what's the best way to go about writing the plugin.
> Hence
[input_log]
type = "LogstreamerInput"
log_directory = "/tmp"
file_match = "hello.log"
[output_s3]
type = "S3Output"
message_matcher = "TRUE"
secret_key = "4fvHMt5lekgPWzxLwUgwb+kcFu7lVi695NxUJ0a7"
access_key = "0BRRE6DFWV2WSVJD3882"
bucket_name = "wego-logs-staging"
path_name = "/hello"
region = "
Hey sorry, could you guys delete/edit my previous message? I have realised
I accidentally exposed my access key and secret key.
On Thu, May 14, 2015 at 2:17 AM, Alex Jiao wrote:
> [input_log]
> type = "LogstreamerInput"
> log_directory = "/tmp"
> file_match = "hello.log"
>
> [output_s3]
> type =
Hey Alex,
You should regenerate your keys, even if the message is deleted people
will still have the cache of the email. I'd do this immediately btw.
On Wed, May 13, 2015 at 6:21 PM, Alex Jiao wrote:
> Hey sorry, could you guys delete/edit my previous message? I have realised I
> accidentally ex
Your code is put together very strangely. The ticker channel is firing
correctly, but once it fires the first time you immediately get trapped
in the for loop that is over the range of the inChan. So you aren't
getting any of the input messages until the first tick fires, but after
it fires you
Hey Rob, thanks a lot for your input. It clears up a lot of doubts
regarding my code. I have rewritten it according to your suggestions and it
works. The ticker now fires at regular intervals as expected, with the
added bonus that the plugin is able to shut down cleanly upon killing the
process. I
BTW, as I am still new to golang and writing plugins, any feedback will be
very useful!
On Mon, May 18, 2015 at 9:15 PM, Alex Jiao wrote:
> Hey Rob, thanks a lot for your input. It clears up a lot of doubts
> regarding my code. I have rewritten it according to your suggestions and it
> works. Th
9 matches
Mail list logo