Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Logstash with Chronicles-Logger (Logback) #46

Closed
msiddiqi opened this issue Aug 16, 2017 · 4 comments
Closed

Using Logstash with Chronicles-Logger (Logback) #46

msiddiqi opened this issue Aug 16, 2017 · 4 comments
Labels

Comments

@msiddiqi
Copy link

Hi, We are currently using ELK Stack (Elastic Search / Logstash / Kibana). We use Logstash TCP appender with logback to push these logs to Logstash in our Scala projects. Is there a way, we use the current logging stack with Chronicle-Logger?

P.S. I have used chronicles-logger (version 1.1.1) from http://repo.spring.io/libs-milestone/ repository.

Thanks,
Muhammad

@TerryW9
Copy link

TerryW9 commented Aug 16, 2017

Hi Muhammad,

Thank you for your question.
We will try to get back to you with an answer as soon as possible.

Best Regards,
Terry

@epickrram
Copy link
Contributor

Hi Muhammad,
what problem are you trying to solve by using chronicle-logger? From what I understand of your stack, you already asynchronously log messages (via logback), that are then sent over the network to Logstash.
Are you trying to reduce the amount of garbage generated by the log messages?

@msiddiqi
Copy link
Author

Actually just trying to see what different components chronicles provides and see how we can use in our environment. "Fast synchronous logging without losing any message before an service crashed" is what I am interesting in here. This should be specially useful for some low latency trade execution related work we are planning to do in future.

@epickrram
Copy link
Contributor

The main difference if you use chronicle-logger is that your log messages will be persisted to disk on the local machine. Persistence via chronicle-queue will faster than writing to a standard file, and you can choose a more compact/efficient format (i.e. BINARY) for storing the messages.

The drawback of this approach is that you no longer have all your log messages in a single place for easy searching. If that is still a requirement, then you'd need to create another component/process to read the log files and send them off to logstash. In a crash scenario, you'd then need to make sure you don't send duplicate log entries to logstash on restart.

If you'd like some support in designing a solution, Chronicle Software can provide consultancy services to help you get the most out of the open-source products. You can find contact details on the website:

http://chronicle.software

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants