Hi Peter,
Good idea about the class name. I'll look into it.
I'm curious to know what you would use the raw kstat information
for. We're always looking for ideas on how to the system more
observable in a way that's useful for customers.
Thanks,
Rich
Peter Tribble wrote:
> Hi,
>
> I've been having a look at the new fsstat utility that's just
> integrated,
> and it's very neat.
>
> One thing slightly bothers me though, and that's related to the naming
> scheme of the underlying kstats:
>
> module: unix instance: 0
> name: vopstats_ufs class: misc
>
> Hm. Picking these out isn't as easy as it might be. I don't suppose that
> a lot can be done about the main triplet, but wouldn't a more infomative
> class name (eg. "fsstat") be more helpful?
>
> According to kstat(3kstat) "This field can be used as a filter to
> extract related
> kstats", so assigning a unique class name seems useful.
>
