cf-charmers team mailing list archive

[Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>]

Hi Alex, there seems to be some confusion here. What is your goal. Afaik
its to use ELK stack with cf log subsystem. In that case why are you doing
it in the cf charms?, for cf apps you do it via the cf cli outside of the
juju on a per cf app basis.  At that point you need to entirely separately
from cf charm/bundle setup an elastic search stack that has a syslog
entrypoint that can be used with cf cli.

juju-info is an implicitly provided relation interface of all services, its
primarily used to allow subordinates to relate to services that without
 having custom pre-built awareness of them. ie apply cross cutting concerns
like logging and monitoring without modifying the principal.

for the entirely different use case of paas infrastructure logging,  its
also unclear why you think logstash agent is nesc, logstash can provide the
syslog entrypoint and the extant trusty rsyslog forwarder charm can be used
to forward to a syslog entry point.

-k


On Tue, Sep 9, 2014 at 10:11 PM, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> Hi, folks.
>
> As Kapil sayed it is possible to connect CF to rsyslog through
> rsyslog-forwarder-ha charm. Using this charm will create constrain for Log
> Traffic Container: it will be required to work with default 514 port. I
> already checked this configuration.
>
> What goes to logstash, I just checked that it has the similar approach.
> logstash-agent should be connected with syslog provider (Log Traffic
> Controller in our case). Will check in the next few hours.
>
> What is your attitude to making syslog port for Log Traffic Controller
> unchangeable?
>
> I have other short question. I saw relation with juju-info name several
> times. Could you say what is it for?
>
>
> Thank you,
> Alex L.
>
> --
> Mailing list: https://launchpad.net/~cf-charmers
> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cf-charmers
> More help   : https://help.launchpad.net/ListHelp
>
>