JDBC input plugin

(Gianluca Valentini) #1

is there somebody that can help my to understand how to implement a generic JDBC input for Graylog?

I haven’t found anything in the Marketplace. Are there some guidelines that I can use?

Thanks a lot

(Jochen) #2

For a generic plugin development documentation, take a look at http://docs.graylog.org/en/2.3/pages/plugins.html.

Also make sure to take a look at the existing input plugins for Graylog, e. g. https://github.com/graylog-labs/graylog-plugin-redis

(Gianluca Valentini) #3

Thanks a lot for your suggestion.

I’d like to understand too, the complete data track, from the target machine, with the sidecar and the input plugin


(Jochen) #4

If you’re going to use a separate log shipper anyway, you could as well just use the Logstash and its JDBC input and GELF output.

(Gianluca Valentini) #5

Hi @jochen thanks again for your help.

Just for my understanig, can you explain me what is the data lifecycle in graylog experience?
I mean, when I write an input, for example something like redis plugin, who send the message to it if I have 2 different machine where Graylog and Redis are installed?

I suppose that I need to install something like sidecar, isn’t it? Please correct me if I’m writing something wrong, I’d like to understand.


(Jochen) #6

The term “input” is to be taken quite liberally. It’s simply a source of messages for Graylog.

Inputs can open network sockets like the Syslog inputs, pull data from somewhere else like the Redis inputs, or simply generate arbitrary data like the “Random HTTP message generator” input.

You don’t have to install the Graylog Collector Sidecar or any other log shipper (such as Filebeat, Logstash, or NXLOG) if Graylog is able to access the message source directly (again, take a look at the Redis plugin).

(Gianluca Valentini) #7

Thanks, @jochen, you really made it all much more clear.

Thanks a lot

(system) #8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.