https://github.com/teragrep/snw_01
Table data-pump export to relp syslog
https://github.com/teragrep/snw_01
audit-log data-export data-pump export java logging relp relp-client servicenow servicenow-api syslog
Last synced: about 2 months ago
JSON representation
Table data-pump export to relp syslog
- Host: GitHub
- URL: https://github.com/teragrep/snw_01
- Owner: teragrep
- License: agpl-3.0
- Created: 2023-10-27T12:02:26.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-01-09T10:08:35.000Z (about 2 years ago)
- Last Synced: 2024-04-17T19:13:17.198Z (almost 2 years ago)
- Topics: audit-log, data-export, data-pump, export, java, logging, relp, relp-client, servicenow, servicenow-api, syslog
- Language: Java
- Homepage:
- Size: 50.8 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.adoc
- License: LICENSE
Awesome Lists containing this project
README
= 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`
[cols=3,2]
|===
|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
[source,]
----
systemctl start snw_01
----
== Contributing
// Change the repository name in the issues link to match with your project's name
You can involve yourself with our project by https://github.com/teragrep/snw_01/issues/new/choose[opening an issue] or submitting a pull request.
Contribution requirements:
. *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.
. Security checks must pass
. Pull requests must align with the principles and http://www.extremeprogramming.org/values.html[values] of extreme programming.
. Pull requests must follow the principles of Object Thinking and Elegant Objects (EO).
Read more in our https://github.com/teragrep/teragrep/blob/main/contributing.adoc[Contributing Guideline].
=== Contributor License Agreement
Contributors must sign https://github.com/teragrep/teragrep/blob/main/cla.adoc[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.