-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Loki Logstash Plugin #1822
Loki Logstash Plugin #1822
Conversation
@cyriltovena @slim-bean Need your thoughts and guidance on this |
499a68a
to
c19554b
Compare
Can you remove the .class and .gem files, basically all artefacts. Feel free to add an .gitignore for that folter. |
Have you considered writing the plugin only in ruby ? I think it would make our life easier since we also have a ruby plugin for fluentd. |
@cyriltovena Ruby is new to me. It would take little more time for me to write the plugin in Ruby. I totally agree that it would be lot easier to maintain the code since we already have fluentd in Ruby. What do you think? If you say let's stick to Ruby, let's go with Ruby. I will close this and create new PR. |
Hey @adityacs, firstly can't thank you enough for all your contributions lately. You are a pleasure to work with and we really appreciate everything you are doing!! I think in this case Ruby would be preferred as adding the java toolchain I think is adding another amount of complication we may not want. It looks like most other logstash plugins are ruby based. |
@slim-bean Yeah Ruby would be better. I just took an easy route since I am familiar with Java 😜 I will work on the Ruby plugin and update this PR. |
I'm not the best but I've been involved a lot lately with the fluentd plugin in Ruby, so don't hesitate to ask question on #loki-dev by pinging me or @slim-bean. |
Sure @cyriltovena |
@slim-bean @cyriltovena Thanks for the feedback. It's a great experience to work with you guys. |
4754a74
to
9b1d683
Compare
Pushed plugin with Ruby code. Have to add add few tests. |
92b9c50
to
6acd391
Compare
@cyriltovena @slim-bean Have added tests and also updated the docs. Kindly requesting you guys to review this Also, let me know if you are able to build and test the plugin. |
Codecov Report
@@ Coverage Diff @@
## master #1822 +/- ##
==========================================
- Coverage 64.75% 64.72% -0.03%
==========================================
Files 122 122
Lines 9271 9271
==========================================
- Hits 6003 6001 -2
- Misses 2853 2854 +1
- Partials 415 416 +1
|
logstash/LICENSE
Outdated
@@ -0,0 +1,202 @@ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@slim-bean do we need to have a license ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No separate license, this would fall under the license for the project itself
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will remove
Can you remove binary artifacts. Feel free to add a .gitignore to this new folder if required. |
data_labels = lbls.merge(@external_labels) | ||
|
||
entry_hash = { | ||
"ts" => event.get("@timestamp").to_i * (10**9) + Time.new.nsec, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's going on here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This converts the timestamp to nano seconds
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have doubts about the new here, may be a test since we know what timestamp are using logstash ;)
"line" => event.get("message").to_s | ||
} | ||
|
||
@Channel.go do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t think you need a go here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not required. Will remove
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually Channel.go
is required here. Since we are using unbuffered channel(i.e without specifying capacity), if we don't use Channel.go
it hangs there without proceeding with the code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hanging is fine, if it is hanging it is probably waiting for the previous batch to be sent.
If you keep it this way, it means for each event, (million of them) create a go routine. That can be huge for the system.
You may want to use buffered but I think it's better to wait, this also signal, don't send more we're busy to the plugin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, got your point. Will make the change
Signed-off-by: Cyril Tovena <[email protected]>
git clone [email protected]:elastic/logstash.git | ||
cd logstash | ||
git checkout tags/v7.6.2 | ||
export LOGSTASH_PATH=`pwd` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice 👍
We are pending with Makefile changes to build this plugin. I will take care of this |
Signed-off-by: Cyril Tovena <[email protected]>
event.to_hash.each { |key,value| | ||
next if key.start_with?('@') | ||
next if value.is_a?(Hash) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should consider the nested fields as well right? Any reason to skip it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They can already create new field out of current field if they want to.
I think logstash is good enough for managing fields that we shouldn't try to do anything.
Now testing/writing docs and charts. Signed-off-by: Cyril Tovena <[email protected]>
One sec I've just finished the code. |
…loki_logstash_plugin Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
Signed-off-by: Cyril Tovena <[email protected]>
* Logstash plugin * include_labels * include_labels * Removes binary. Signed-off-by: Cyril Tovena <[email protected]> * Improve documentation and remove the push path. Signed-off-by: Cyril Tovena <[email protected]> * Move to cmd. Signed-off-by: Cyril Tovena <[email protected]> * Add more precision for jruby. Signed-off-by: Cyril Tovena <[email protected]> * Update docs/clients/logstash/README.md * p Signed-off-by: Cyril Tovena <[email protected]> * ignore Signed-off-by: Cyril Tovena <[email protected]> * remove ignore file/ Signed-off-by: Cyril Tovena <[email protected]> * More precision for installing jruby Signed-off-by: Cyril Tovena <[email protected]> * Rename without Grafana Signed-off-by: Cyril Tovena <[email protected]> * A lot of refactoring and testing. Signed-off-by: Cyril Tovena <[email protected]> * change delay logic * Fully tested version. Now testing/writing docs and charts. Signed-off-by: Cyril Tovena <[email protected]> * Forgot to save merge. Signed-off-by: Cyril Tovena <[email protected]> * working version. Signed-off-by: Cyril Tovena <[email protected]> * Makefile + easier docker build. Signed-off-by: Cyril Tovena <[email protected]> * adds ci to build logstash image. Signed-off-by: Cyril Tovena <[email protected]> * Fix build for logstash. Signed-off-by: Cyril Tovena <[email protected]> * Adds example with helm charts. Signed-off-by: Cyril Tovena <[email protected]> * Fix target to send 10 logs with logstash. Signed-off-by: Cyril Tovena <[email protected]> * Improved documentation. Signed-off-by: Cyril Tovena <[email protected]> * add missing helm add repo for external repo Signed-off-by: Cyril Tovena <[email protected]> * Review comment. Signed-off-by: Cyril Tovena <[email protected]> * Fixes loki service in Promtail. Signed-off-by: Cyril Tovena <[email protected]> * Update loki-stack version Signed-off-by: Cyril Tovena <[email protected]> Co-authored-by: Cyril Tovena <[email protected]>
What this PR does / why we need it:
Logstash plugin for Loki
Which issue(s) this PR fixes:
Fixes #1192
Checklist