Debugging functionality of loggregator

[Johannes Hiemer]

Hi all,

I currently migrated my environment to v177. Since the upgrade I am having serious issues with the loggregator output. Doing a `cf logs app --recent` is empty and `cf logs app`as well. What I am wondering about is, if it is related to the migration towards the metron agent. Communication from CF (latest build) seems properly working:

WEBSOCKET REQUEST: [2014-08-31T19:16:41+02:00]

GET /tail/?app=cbfe0272-b02a-42b6-bbb7-16d6fcde60c2 HTTP/1.1

Host: wss://loggregator.x.x.x.x.xip.io:443

Upgrade: websocket

Connection: Upgrade

Sec-WebSocket-Version: 13

Sec-WebSocket-Key: [HIDDEN]

Origin: http://localhost

Authorization: [PRIVATE DATA HIDDEN]

WEBSOCKET RESPONSE: [2014-08-31T19:16:43+02:00]

HTTP/1.1 101 Switching Protocols

Upgrade: websocket

Connection: Upgrade

Sec-Websocket-Accept: LwcLwdUOBmVcB87+vjGyNfYmCZQ=

What I would be interested in, after looking through the logs of the DEA and the loggregator instance is, if there is well documented way how to debug the functionality of loggregator. The logs do not contain any abnormal contents.

Would be glad for any input or information.

Regards,

Johannes

[Karl Isenberg]

You'll probably get better CF help on the vcap-dev mailing list: https://groups.google.com/a/cloudfoundry.org/forum/m/#!forum/vcap-dev

-Karl

To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+...@cloudfoundry.org.

[René Welches]

Hi Johannes,

Did you upgrade to the latest version of the CLI. We had the same issue with older versions of the CLI.

René

To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+...@cloudfoundry.org.

[Johannes Hiemer]

Hi René,

I am running with the latest version of the CLI. Anyone else with good idea?