Thanks Ketan
Now I am more confused, the libs folder doesn't appear to be being read,
should it be in a path somewhere ?
looking at the api/support page there are no references to that even though
we are on 17.12 i can only imagine its related to this not being a fresh
install onto 17.12. I wouldn't however expect that upgrades in the past
would break this type of process, I have already defaulted the jetty.xml
and removed other logging config files, as being a potential problem but it
hasn't helped.
Socket appender does work (see below), but its output isn't ideal and isnt
an encoder for it or a way to deserialize the output at the logstash end.
<appender name="SOCKET" class="ch.qos.logback.classic.net.SocketAppender">
<remoteHost>MY-LOGSTASH</remoteHost>
<port>3319</port>
<reconnectionDelay>10000</reconnectionDelay>
<includeCallerData>true</includeCallerData>
</appender>
this also confirms its not a comms issue its a problem with either the libs
not being picked up or another issue with logging.
I am convinced this is an issue with the server being upgraded rather than
fresh installed.
Any more help would be appreciated,
Kind regards
Barry
On Wednesday, 10 January 2018 16:14:08 UTC, Ketan Padegaonkar wrote:
>
> This script
> <https://gist.github.com/ketan/66af4070900ef22437e279be71288b35> worked
> for me, I was able to confirm that logs were sent to logback.
>
> On Wed, Jan 10, 2018 at 8:51 PM 'Barry Greenwood' via go-cd <
> [email protected] <javascript:>> wrote:
>
>> Thanks for the update
>>
>> That folder didnt exist on our server, I have added with go permissions,
>> I've added the files but it still isnt working.
>>
>> as this isnt the first issue i've had regarding this recently implemented
>> feature can you please confirm that it works and should the logs show it
>> being loaded ?
>>
>> Many thanks
>>
>> Barry
>>
>>
>> On Wednesday, 10 January 2018 13:56:09 UTC, Ketan Padegaonkar wrote:
>>
>>> The `libs` dir is relative to the working directory of the server/agent.
>>> This should typically be `/var/lib/go-server/libs` or
>>> `/var/lib/go-agent/libs`. I'll update the documentation to clarify this.
>>>
>>>
>>> On Wed, Jan 10, 2018 at 6:29 PM 'Barry Greenwood' via go-cd <
>>> [email protected]> wrote:
>>>
>> Hi all
>>>>
>>>> I've now got logback able to log to local files with access requests
>>>> and other logs, I am now hoping to ship these to an external logstash
>>>> server
>>>>
>>>> reading
>>>> https://docs.gocd.org/current/advanced_usage/logging.html#advanced-logging-features
>>>>
>>>> this should be possible, however its a little abiguous with "download
>>>> all logstash-logback-encoder jars and dependencies into libs dir:"
>>>>
>>>> I presume its a java library folder as these are jar files but testing
>>>> with these in several places that are in the java.library.path, it isn't
>>>> working.
>>>>
>>>> Has anyone else tried to get this working and had success ?
>>>>
>>>> Regards
>>>>
>>>> Barry
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "go-cd" group.
>>>>
>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>
>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
