[syslog-ng] Use receiving file name / path as a macro on the server

Thanuje Ashwin Nallaperuma thanuje88 at gmail.com
Tue Mar 3 11:43:02 CET 2015


Hi Vikrot,

$HOST gives the IP address or the FQDN according to the settings
I am looking for a way to pass the log file path as a string to the
syslog-master and use it


On Tue, Mar 3, 2015 at 3:46 PM, Juhász, Viktor <viktor.juhasz at balabit.com>
wrote:

> Hi,
>
> If I understand you well, You should use HOST macro in the file name.
>
> BR,
> Viktor Juhasz
>
> On Tue, Mar 3, 2015 at 10:57 AM, Thanuje Ashwin Nallaperuma <
> thanuje88 at gmail.com> wrote:
>
>> Hi Sandor,
>>
>> I do not need to maintain the file hierarchy
>> I just one to transfer the file path to the server and use it as a macro
>> on the server side
>> because the path is the only way I am able to identify the files I send
>> as they have the same name and same content
>>
>> On Tue, Mar 3, 2015 at 1:35 PM, Sandor Geller <sandor.geller at ericsson.com
>> > wrote:
>>
>>> Hi,
>>>
>>> On 03/03/2015 05:15 AM, Thanuje Ashwin Nallaperuma wrote:
>>> > Hi all,
>>> >
>>> > I have multiple files with the same content on the syslog-ng client
>>> > These files are stored on different locations with the same file name
>>> > and same content
>>> > After receiving I want to store these files with different names on
>>> > sysog-ng server
>>> > Is there any way I could use the filepath or filename of the receiving
>>> > file as a macro
>>> > or any way to achieve this..?
>>>
>>> I'm having some trouble understading what you're after. Do you want to
>>> simply transfer files from remote systems to a central place and keep a
>>> similar filesystem hierarchy on the central location as well? For such a
>>> purpose syslog isn't the preferred way as it isn't a generic purpose
>>> transport so use something else like rsync.
>>>
>>> There are ways to manipulate messages on the originating side (for
>>> example by adding tags to the syslog-ng source definitions) and
>>> encapsulating the extra information into the message payload you'll be
>>> able to extract the information on the remote side - but I'm not sure it
>>> worths the effort.
>>>
>>> hth,
>>>
>>> Sandor
>>>
>>>
>>> ______________________________________________________________________________
>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>> Documentation:
>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>
>>>
>>
>>
>> ______________________________________________________________________________
>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>> Documentation:
>> http://www.balabit.com/support/documentation/?product=syslog-ng
>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>
>>
>>
>
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20150303/898b47cf/attachment-0001.htm 


More information about the syslog-ng mailing list