|
Loggregator/Doppler Syslog Drain Missing Logs
Hi Michael First question that springs to mind when I see ~50% - how many zones are you running as part of your setup? ("every other log" sounds like a round-robin to something dead or misconfigured.)
Hi Michael First question that springs to mind when I see ~50% - how many zones are you running as part of your setup? ("every other log" sounds like a round-robin to something dead or misconfigured.)
|
By
Erik Jasiak
· #1949
·
|
|
Loggregator update - removing /varz shim
One last update for the weekend everyone - Loggregator is finally going to remove the "/varz" shim [1]. This should affect - hopefully, no one: the shim was there from when loggregator was first in de
One last update for the weekend everyone - Loggregator is finally going to remove the "/varz" shim [1]. This should affect - hopefully, no one: the shim was there from when loggregator was first in de
|
By
Erik Jasiak
· #1845
·
|
|
Loggregator Community Survey #2 - TCP for Metron<-->Doppler
Greetings again CF community! As part of the new dropsonde point proposal[1], the team would have to implement some tough sizing choices related to UDP packets, and the likelihood of larger packets ge
Greetings again CF community! As part of the new dropsonde point proposal[1], the team would have to implement some tough sizing choices related to UDP packets, and the likelihood of larger packets ge
|
By
Erik Jasiak
· #1844
·
|
|
Loggregator Community Survey #1 - still use the old metron 51160 endpoint?
Greetings CF community! The loggregator team is actively trying to clean up its footprint. To that - does anyone still use the "old" metron endpoint, on port 51160 by default? [1] We are considering t
Greetings CF community! The loggregator team is actively trying to clean up its footprint. To that - does anyone still use the "old" metron endpoint, on port 51160 by default? [1] We are considering t
|
By
Erik Jasiak
· #1843
·
|
|
stdout.log and stderr.log not show in CF197 with loggregator enabled
Dan is correct - "cf file" for getting stdout/stderr files directly was deprecated some time ago. I'll try to locate when that happened (it was before my time.) From the cli, "cf logs" for streaming,
Dan is correct - "cf file" for getting stdout/stderr files directly was deprecated some time ago. I'll try to locate when that happened (it was before my time.) From the cli, "cf logs" for streaming,
|
By
Erik Jasiak
· #1456
·
|
|
Collector fix for default data tagging
Thanks Marco - for everyone else on the list, we reached out to Marco after this email, and opened a tracker story[1] to do deeper analysis of collector tags that may change. Thus far we have found no
Thanks Marco - for everyone else on the list, we reached out to Marco after this email, and opened a tracker story[1] to do deeper analysis of collector tags that may change. Thus far we have found no
|
By
Erik Jasiak
· #1398
·
|
|
Collector fix for default data tagging
Hi all, The loggregator team has been working to maintain metric parity between the CF collector[1] and the firehose[2] in the short term.This is to help CF operators feel confident they can move from
Hi all, The loggregator team has been working to maintain metric parity between the CF collector[1] and the firehose[2] in the short term.This is to help CF operators feel confident they can move from
|
By
Erik Jasiak
· #1392
·
|
|
Firehose vs Pivotal Ops metrics
Hi Qing, First, Ops Metrics is a closed-source addition to Pivotal Cloud Foundry. The metrics exposed by Ops Metrics today come from the collector[1] and tomorrow from both the collector and firehose.
Hi Qing, First, Ops Metrics is a closed-source addition to Pivotal Cloud Foundry. The metrics exposed by Ops Metrics today come from the collector[1] and tomorrow from both the collector and firehose.
|
By
Erik Jasiak
· #1377
·
|
|
max length with Dropped log message: message too long (>64K ...)
Hi James / cf-dev There are tests, but the corner case fell through the cracks - bug[1] and additional test request[2] added. For everyone else, most of the discussion appeared to happen in Slack. Sum
Hi James / cf-dev There are tests, but the corner case fell through the cracks - bug[1] and additional test request[2] added. For everyone else, most of the discussion appeared to happen in Slack. Sum
|
By
Erik Jasiak
· #1354
·
|
|
App syslog drain performance improvements
Hi CF community, The Loggregator team has two medium-impact changes as part of CF v215. * First, we fixed a bug causing slower performance with application syslog drains. [1][2] The impact is that dop
Hi CF community, The Loggregator team has two medium-impact changes as part of CF v215. * First, we fixed a bug causing slower performance with application syslog drains. [1][2] The impact is that dop
|
By
Erik Jasiak
· #1329
·
|
|
Logstash and Multiline Log Entry
Hi Steve and Simon; hello again Mike, First, apologies for the delay in reply on this one- I've also been trying to come up with a simple, short answer to this problem. I failed. Here are the high-lev
Hi Steve and Simon; hello again Mike, First, apologies for the delay in reply on this one- I've also been trying to come up with a simple, short answer to this problem. I failed. Here are the high-lev
|
By
Erik Jasiak
· #1194
·
|