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

arcsight module: passthrough kafka and tcp options (WIP) #9954

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

yaauie
Copy link
Member

@yaauie yaauie commented Aug 30, 2018

Target: master, 6.x

Resolves: #9746

Passthrough options from Kafka- and TCP-Input Plugins to the Arcsight Module, in order to add support for TLS/SSL that are already available in the plugins to the module.

At this point I'm looking for feedback on general approach.

TODO:

  • documentation: since we are passing through these options directly to the respective input plugin without providing additional defaults, and we avoid talking about the Event Broker as Kafka in the docs or the SmartConnector as TCP in the docs, I'm not sure the best way to document without duplicating everything in the respective plugins.
  • tests: there are a lot of combinations of settings that are available, and I will need find the right way to add tests that validate the intended behaviour, since the module currently does not have any tests

@karenzone
Copy link
Contributor

@karenzone. Take a look with an eye toward this:

documentation: since we are passing through these options directly to the respective input plugin without providing additional defaults, and we avoid talking about the Event Broker as Kafka in the docs or the SmartConnector as TCP in the docs, I'm not sure the best way to document without duplicating everything in the respective plugins.

@acchen97
Copy link
Contributor

@karenzone I think we can probably just list the options again in the ArcSight module docs, similar to what we did with the Azure module config options. We'd have to find a way (or be diligent) around updating these module options if the underlying plugin options change. I'd expect these changes to be relatively uncommon given most of these options are quite stable at this juncture.

@acchen97
Copy link
Contributor

acchen97 commented Nov 26, 2018

@yaauie @guyboertje should we be closing this given it looks like it's been superseded by @guyboertje PR?

#10056

@guyboertje
Copy link
Contributor

Damn, I didn't check whether Ry had done any work already.

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

Successfully merging this pull request may close these issues.

[ArcSight Module] Add TLS support for Smart Connector input option
7 participants