Hi Ponraj, It could be that your token may have expired. Also, silly question but you may want to check that you have access to the app in question. A good way to verify this is by running `cf logs

Assk, can you confirm that the same scope (abacus.usage.write) is sufficient to retrieve usage ? Piotr

We have enabled scope based authorization for REST endpoints at usage collector and usage reporting service. While we are working on using system OAuth bearer access token at internal Abacus pipeline,

Hi Ben, I'm adding a 'processed' time field to the usage docs, hoping that'll help maintain the history of usage within the slack window we've been discussing here (more precisely that will help you

Great! Thanks Jim. Sounds completely reasonable. Hopefully we can keep this thread moving and help derive some future designs out of it. Would you prefer to keep this discussion on the mailling

We are using it. Though we plan to fix this. If we could get a general timeline for what release you plan to remove it in then we can plan to remove it from our code by then. Mike

As many of you are aware, the Cloud Foundry Java Client has been a bit neglected lately. There are various reasons for this, but today I’m pleased to announce that we’ve begun a V2 effort and

New Loggregator PM chiming in. This is definitely on the Loggregator roadmap. Only issues are selecting a design and finalizing (as much as is ever possible) where it lives in the priority order. We

Thanks Phil! I couldn't make the call so this saved my bacon. Mike alexander.lomov(a)altoros.com> wrote:

Any thoughts on what protocol this socket would listen too? Raw Dropsonde? Syslog? I've been thinking about your questions regarding the '\' approach: As Erik mentioned in the last thread,

There's no technical reason why it can't be used for deployments, but there are plenty of bug and security fixes that have gone out in later releases. Joseph CF Release Integration Team

application_version is mostly an internal cloud foundry concern. The DEAs broadcast the application version they are running, and the health manager uses that with what version it expects to be

You don't need to do the $(cf oauth-token | grep bearer) all within the curl command. Perhaps the auth issue will be more apparent if you break it down into each individual step. What happens if you

Is there an equivalent of xray or ltc visualize for diego enable CF environment? Thanks, Tom

Dear Customer, This is to confirm that one or more of your parcels has been shipped. Please, open email attachment to print shipment label. Sincerely, Wayne Mays, FedEx Operation Agent.

Hi, Sorry for the spam. Latest update : I am able to execute the command. But I dont have authorization. I get the message. You are not authorized. Error: Invalid authorization -- Ponraj

Hi Rohit, Now I am able to resolve the host, but the command doesnt seem to work. It says, curl: option --guid)/recentlogs: is unknown -- Ponraj

That’s so handy. Thank you very much, Phil.

Hi Rohit, I am using the cf-release version 211, CC API version 2.28.0 , CLI version-6.12.2. Also I replaced "loggregator" with "doppler" . But still its not able to resolve the host. For instance,

The status codes are pretty consistent. What is being affected are related, aka, nested routes which always returned a 201 on DELETE. Any delete on a resource returns a 204 if done immediately or