Skip to content

Conversation

@mstopa-splunk
Copy link
Contributor

No description provided.


# Define a common configuration block for all servers
map $server_port $upstream_name {
514 stream_syslog_514;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably we also need tell that we can use port segregation, it will increase performance:

SC4S_LISTEN_DEFAULT_TCP_PORT=514,515,516,517

@ikheifets-splunk
Copy link
Contributor

@mstopa-splunk @rjha-splunk Are we have a plan to create ansible playbook that will bootstrap sc4s instances with LB?
I understanding that some of the settings are optional, but are we have such plans?

@rjha-splunk
Copy link
Collaborator

@mstopa-splunk @rjha-splunk Are we have a plan to create ansible playbook that will bootstrap sc4s instances with LB? I understanding that some of the settings are optional, but are we have such plans?

@ikheifets-splunk not yet

@mstopa-splunk mstopa-splunk marked this pull request as ready for review January 3, 2025 10:30

proxy_bind $remote_addr:$remote_port transparent;

health_check udp;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

    match server_ok {
        send "GET /health HTTP/1.0\r\n\r\n";
        expect ~* '"healthy"';
    }

    # Define connections to each of your upstreams.
    # Include `proxy_bind` and `health_check`.
    server {
        listen        514 udp;
        proxy_pass    stream_syslog_514;
        proxy_bind $remote_addr:$remote_port transparent;
        health_check interval=1 match=server_ok port=8080;
    }

@mstopa-splunk mstopa-splunk changed the base branch from main to develop January 16, 2025 11:09
@mstopa-splunk mstopa-splunk merged commit 623cea7 into develop Jan 16, 2025
10 of 19 checks passed
@mstopa-splunk mstopa-splunk deleted the nginx_with_sc4s branch January 16, 2025 11:10
@github-actions github-actions bot locked and limited conversation to collaborators Jan 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants