Skip to content

Conversation

@guillermo
Copy link

The normal use case for this patch, is for common login things. For example, put application errors or user actions into the syslogs makes it possible to track application errors in realtime while also saving it to files.

One problem with the tests was found in the spec that tries to check content integrity. That test should be disabled as (explained in the documentation) the syslog format should be less that 1024 bytes.

Only the value in the "content" key on the hash passed to publish will be transmited.

In the subscription part, the rest of the information of the syslog will be available as more keys in the message received.

@guillermo
Copy link
Author

I have the feeling that this will not be merged...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant