Skip to content

teragrep/snw_01

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Log to RELP forwarder (snw_01)

Requirements

java-11

Configurations

All configuration settings are passed as system properties. They can be edited with systemctl edit --full snw_01

Property Default value Description

log4j2.configurationFile

file:///opt/teragrep/snw_01/etc/log4j2.xml

log4j2 configuration location

syslog.appname

snw-02

Relp application name

syslog.hostname

localhost.localdomain

Relp hostname

tableApi.version

v2

API version

tableApi.sysParamLimit

1000

API system parameter limit

tableApi.tables

sysevent,syslog_transaction

Tables to fetch

tableApi.username

Username for authenticating to the API

tableApi.password

Password for authenticating to the API

tableApi.url.scheme

http

Protocol to use when connecting to the API

tableApi.url.host

localhost

API host

tableApi.url.port

8080

API port

statestore.directory

var

Statestore directory, relative to current working directory

scheduler.interval

2000

Fetch interval

proxy.enabled

false

Is proxy enabled

proxy.host

localhost

Proxy hostname

proxy.port

3128

Proxy port

proxy.authentication.enabled

false

Does proxy require authentication

proxy.authentication.username

Username for proxy authentication

proxy.authentication.password

Password for proxy authentication

relp.connection.timeout

5000

Relp connection timeout, in milliseconds

relp.transaction.read.timeout

5000

Relp transaction reading timeout, in milliseconds

relp.transaction.write.timeout

5000

Relp transaction writing timeout, in milliseconds

relp.connection.retry.interval

5000

Relp connection retry interval, in milliseconds

relp.connection.port

601

Relp target port

relp.connection.address

localhost

Relp target address

Usage

systemctl start snw_01

Contributing

You can involve yourself with our project by opening an issue or submitting a pull request.

Contribution requirements:

  1. All changes must be accompanied by a new or changed test. If you think testing is not required in your pull request, include a sufficient explanation as why you think so.

  2. Security checks must pass

  3. Pull requests must align with the principles and values of extreme programming.

  4. Pull requests must follow the principles of Object Thinking and Elegant Objects (EO).

Read more in our Contributing Guideline.

Contributor License Agreement

Contributors must sign Teragrep Contributor License Agreement before a pull request is accepted to organization’s repositories.

You need to submit the CLA only once. After submitting the CLA you can contribute to all Teragrep’s repositories.