In order to get a list of the noisy neighbour applications up until now (up until the latest 4.0.0 release ) we were using v3.1.0 and the following command to get the GUIDs of the applications together with the log stats:
After we get the guids we run another CF API call to get the organization and space where the app is running:
cf curl /v3/apps?guids=GUID[i]&include=space,space.organization and the end we show everything as a table.
Now we've installed the latest version of the log-cache cli plugin and we've got an error that the --guid switch can only be used with --source-type=platform. Therefore we've tested with:
cf log-meta --noise --sort-by=rate --guid
and in the output we've found guids and names of the CF's system components like:
Are the GUIDs only from running applications? Can we simply run the output through GUID validator to filter out the system components and leave the application guids only?
Is there some other way to get only the guids of the applications?
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
Why is the --guid flag only available with --source-type=platform? I personally think that this does not make any sense as
the platform components don't have guids.
The output of the command cf log-meta --noise --guid --sort-by=rate --source-type=platform is like:
In CF, the application names are unique only in a space and to identify an application globally an app guid is needed.
At the moment the command with --source-type=application parameter returns the app names.
The only option to get app guids that I've found up until now is to get the apps and platform data together and then to filter out everything that does not have a guid format.
The command is: cf log-meta --noise --guid --sort-by=rate
From a usability point of view the operators can not do much about the platform logs, so their focus is on observing how the applications behave. With the v4 of the plugin the only way to correctly identify the apps is to get all the log-meta data like in the last example and filter out the platform components.
Activity
cf-gitbot commented on Oct 27, 2020
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
chombium commented on Nov 26, 2020
Few more further questions and observations:
Why is the --guid flag only available with --source-type=platform? I personally think that this does not make any sense as
the platform components don't have guids.
The output of the command cf log-meta --noise --guid --sort-by=rate --source-type=platform is like:
In CF, the application names are unique only in a space and to identify an application globally an app guid is needed.
At the moment the command with --source-type=application parameter returns the app names.
The only option to get app guids that I've found up until now is to get the apps and platform data together and then to filter out everything that does not have a guid format.
The command is: cf log-meta --noise --guid --sort-by=rate
From a usability point of view the operators can not do much about the platform logs, so their focus is on observing how the applications behave. With the v4 of the plugin the only way to correctly identify the apps is to get all the log-meta data like in the last example and filter out the platform components.