Get a list of all Knowledge Centers' names and sizes

It's not pretty and it is clunky but you can navigate to the "All Objects" view, filter by Folder and Search using "Knowledge Center" (assuming your KCs are all named this way):

You can then open the properties of each to get the contents/size value.

Thanks Stewart. Are there any plans in place to display folder sizes in an easier-to-view method? 

Sorry, I know of no such plans. In the meantime here's something I've cooked up. It relies on the Content Tools plug-in from the App Market:

a!localVariables(
  local!ids: fn!enumerate(2000) + 1300,
  local!contentObjects: a!forEach(
    items: local!ids,
    expression: fn!getcontentobjectdetailsbyid(fv!item)
  ),
  local!potentialKCs: a!forEach(
    items: local!contentObjects,
    expression: if(
      fv!item = "No object with this ID has been found",
      null,
      fn!split(fv!item, ",")[5]
    )
  ),
  local!KCIds: local!Ids[wherecontains(
    " Type: Knowledge Center", local!potentialKCs
  )],
  a!forEach(
    items: local!KCIds,
    expression: fn!concat(
      fn!knowledgecenter(fv!item, "name"),
      ": ",
      fn!round(fn!knowledgecenter(fv!item, "size")/1024,2),
      "KB (",
      "Number Of Documents: ",
      fn!knowledgecenter(fv!item, "numberOfDocuments"),
      ")"
    )
  )
)

Output for me is this:

You may have to adjust the starting point for where User-defined KCs come into play (I've set mine at 1300 in Line 2 of the code) and I've set my upper bound as 2000 above this which finds all the ones I can see in the All Objects view I posted about earlier.

In the spirit of understanding what you'd like to see...would a tab on the 'Monitor' view (both at individual Application level, and at all Applications level) that showed the KCs (with their properties) with a tree of the folders/sub-folders with similar properties meet your need? 

Thanks for this, Stewart. I'll give it a try

As for your other comment, yes something baked into the Monitor view as you described would be great. To be able to see all KCs (tree view) and their properties in a sortable columns (ie: sort  KC by size). Similar to Designer view that has columns for Name, Description, Last Modified but to have additionals columns for size/number-of-files. Something like that. 

As for your other comment, yes something baked into the Monitor view as you described would be great. To be able to see all KCs (tree view) and their properties in a sortable columns (ie: sort  KC by size). Similar to Designer view that has columns for Name, Description, Last Modified but to have additionals columns for size/number-of-files. Something like that. 

I have found a registered Use Case for exactly this in the Appian Product backlog. All I can about such backlog items is that they are prioritized according to a number of different factors, and I cannot tell you when or even if) this will ever make it into the product. But rest assured there are other customers who also want to see this.

That's great to hear, Stewart. Many thanks for the feedback.

I may have found a way of deriving this dynamically using the content from the healthcheck files, log reader and content tools plug ins. This works quite well in our Development Environment. 

a!localVariables(
  
  
  /*Read Health Check log file for list of folders to get the log data*/
  
  local!logFile: 
  fn!readcsvlog(
    csvPath: "health-check/hc-document-folders.csv",
    filterColumName: "Type",
    filterOperator: "contains",
    filterValue: "Knowledge",
    headers: {"UUID","Parent UUID","Name","Type","# of Author Groups","# of Viewer Groups","# of Inherited Author Groups","# of Inherited Viewer Groups","Is KC Auto Approved for Read Only Access?","Role Map"}
    
    
    
  ),
  
  /*Only require the UUID from the File - Would have used Excel Tools query logs function but this does not support the health check directory yet*/
  
  local!kcUUID: a!forEach(
    items: local!logFile.rows,
    expression: split(fv!item,",")[1]
  ),
  
  
  /*Using content tools functions convert the UUID to internal ID*/
  /*As a text string is returned need to break the string up into component parts - the internal ID is the 2nd entry and then */
  /*we only want the value after the : value */
  /*KC deletions can occur and so the getcontent fucntion will return object doesnt exist message*/
  
  local!kcDetails: 
    a!forEach(
    items: local!kcUUID,
    expression: 
      a!localVariables(
        local!contentObject: getcontentdetailsbyuuid(fv!item),
        local!split: split(local!contentObject, ","),
        local!kcId: if(count(local!split) > 1, tointeger(split(local!split[2],":")[2]), null),
        local!kcId
      )
    
  ),
  
  
  /*Remove null values - this will remove entries where the KC has been deleted post HealthCheck file creation*/
  local!filteredKCDetails:  reject(a!isNullOrEmpty, local!kcDetails),
  
  /*Now for each entry we can get the desired values using the KC details*/
  
  
  local!output: a!forEach(
    items: local!filteredKCDetails,
    expression: 
    {
      name: fn!knowledgecenter(fv!item, "name"),
      numberOfDocuments: fn!knowledgecenter(fv!item, "numberOfDocuments"),
      sizeInKB: fn!round(fn!knowledgecenter(fv!item, "size")/1024,2),
      sizeinMB: fn!round(fn!knowledgecenter(fv!item, "size") / 1024 / 1024, 2),
      createdBy: fn!knowledgecenter(fv!item, "creator")
      
    }
    
  ),
  local!output
  
  
  
)

Hi paulc919 ... very interesting! Thanks for this. Will give it a go this week and keep you posted.

paulc919 this works great! Thank you for this.

Brill ! Glad to hear this ... the only downside is that it wont pick up new KC's until the Healthcheck report has run. I've extended our housekeeping app to run that logic nightly to display on a record the KC overview providing developers the ability to drill into the KC to see the document meta data ... its been quite an eye opener to see how many "old" files we had laying around on our DEV system.