Alberto Zaccagni

I've written a quick fix to that issue. You should update to 0.1.2 to get it. I still have to make sure that the issue is not showing anymore even...

Is the issue fixed for you?

I'm closing this as the upcoming release will change a lot, most likely will fix the issue because it's the whole point of it.

I thought that was fixed by the work we did 3 years ago. Do you have some code I can use to reproduce the issue? I will tackle this once...

Yes as you said I think the actions are: * retry on error * don't always write the policy on `ensureGroupPresent` I will tackle this after the upgrade lands on...

Hi @drmmr763, I don't have plans to support client side at the moment. I am open to suggestions or PRs though.

There are a few [examples](https://github.com/lazywithclass/winston-cloudwatch/tree/master/examples), none about `messageFormatter` though... but it might also be that I screwed up somewhere during the upgrade to the newer APIs. I will add an...

I've just tested this after reading the source code and this example works for me: ``` var winston = require('winston'), WinstonCloudWatch = require('../index'); winston.add(new WinstonCloudWatch({ messageFormatter: function() { return 'will...

@Carlovan @tiborbaksa hello and sorry for the delay, I've been quite busy on both work and non-work related issues. Is this still relevant? From what I remember by using `messageFormatter`...

So you want to be able to do ```JS winston.createLogger({ exitOnError: false, transports: [], format: winston.format.printf(customFormatter) }); ``` and rely on Winston's default, is that correct?