I've been working with OC Report for a few days now in our lab environment. One of the abilities I'm looking for is for OC Report to be able to have access to the DFM custom comment fields I have added to objects (e.g., objects like volumes, vfilers, etc...). This metadata is key for me to be able to create reports against. For example, here is a volume I have and all the potential comments that could have a values:
Object Id: 1243
Object Name: sdlabfs01:/ralph1
Object Type: Volume
CIFS AD Domain:
An example custom report would be one where I group all volumes based on the wApp field.
The issue I'm having is that I'm not seeing these custom fields as available items to key off of -- is there a DFM database view that I need to enable or some other configuration setting in OC Report? This capability is where I'll find most of the value from OC Report - thanks!
I don't have the Error Retrieving Data in OC Report so I'm not sure if I need to enable these DFM database views? I've been scouring the NOW knowledgebase, community and Admin guides for DFM but can't see how to enable them or even check if they are enabled or disabled. Thanks.
In OCR 1.0 version, unfortunately we collect only the "Comments" data from all the storage objects. I understand using "Custom comments field" is already a practice, but just want to check if you are using Resource Groups in DFM? for the use-case you had mentioned, one way to solve is to group the objects (volume, storage,...) as Resource Groups and you can use OCR report based on that.
We have comment field information of aggregate, volume, storage etc acquired from OnCommand/DFM server by OnCommand Report. If the information is available as part of this field. We can acquire this.Please refer to the screenshot attached.
OnCommand Report does not have the ability to pull custom fields from OnCommand/DFM server in this release. If a new field is defined in DFM server and if the expectation is whether OnCommand Report can pull in as part of DFM servers consolidation, this version of OnCommand Report cannot do that.
Well, thanks for clearing this up. We do already use Resource groups to a certain extent, but I'm concerned about group sprawl since there are potentially hundreds of different values for some of our metadata (custom fields). Simply tagging our objects with these key/value pairs is one way to control that. It would be helpful if this custom reporting capability could be added to the tool -- is there some way I can make this a feature request? Thank you.