Re: SCSI and dmesg

On Thu, Nov 29, 2018 at 11:08 AM Brooks Davis <brooks_at_freebsd.org> wrote:

> On Thu, Nov 29, 2018 at 11:01:01AM -0700, Alan Somers wrote:
> > On Thu, Nov 29, 2018 at 10:49 AM Warner Losh <imp_at_bsdimp.com> wrote:
> >
> > >
> > >
> > > On Thu, Nov 29, 2018 at 8:09 AM Alan Somers <asomers_at_freebsd.org>
> wrote:
> > >
> > >> On Mon, Nov 26, 2018 at 3:57 PM Warner Losh <imp_at_bsdimp.com> wrote:
> > >>
> > >>> On Mon, Nov 26, 2018 at 3:32 PM Maxim Sobolev <sobomax_at_sippysoft.com
> >
> > >>> wrote:
> > >>>
> > >>> > Somebody needs to make collection/submission automatic and make a
> port
> > >>> out
> > >>> > of it, so that it's as easy as pkg install dmesg_survey &&
> > >>> > dmesg_survey_enabled="YES" in the /etc/rc.conf. JIMHO. I'd gladly
> make
> > >>> it a
> > >>> > default on all dev boxes within our organization. Might also make a
> > >>> nice
> > >>> > SoC project idea.
> > >>> >
> > >>>
> > >>> It's barely a weekend hack, since with the curl 1 liner 95% of what
> you
> > >>> want is there.
> > >>>
> > >>> This service isn't suitable, though, to have it in rc.conf, I don't
> > >>> think,
> > >>> unless it's updated only when there's a material change...
> > >>>
> > >>> And I'd rather we get more nuanced data than dmesg can provide if we
> were
> > >>> to do the data collection. The admonition to submit to this site was
> one
> > >>> of
> > >>> expedience...
> > >>>
> > >>> Warner
> > >>>
> > >>
> > >> Sounds like somebody needs to adopt sysutils/bsdstats.  It's a great
> > >> start, but it needs some TLC.
> > >>
> > >
> > > Except there's no available data from it. And it's not a great start,
> but
> > > a terrible one. It gathers the wrong things.
> > >
> > > Warner
> > >
> >
> > What do you mean "no available data"?  Are you saying that you'd prefer
> > direct access to the server rather than access through the web UI?  I'm
> > sure Scrappy would allow that.  He's implied that he'd like some help
> with
> > the server.  What I like about bsdstats is that it's much more structured
> > than your dmesg service.  Instead of a big long string, it gathers
> > structured info with sysctl, pciconf, and pkg.  Plus, it already has a
> > port, it's integrated into periodic(8), and it has a website.  If it
> omits
> > some information that you would like to see, then you should enhance it;
> > not replace it.
>
> The data isn't available through the UI because it's broken.  Try
> drilling down to find all the NIC types for example and you'll get:
>
>         ERROR !!
>
>         an e-mail has been sent to the staff
>         we are sorry for this problem
>
> I've reported this multiple time and at least once Scrappy claimed it
> was fixed, but it wasn't.
>
> -- Brooks
>

Try drilling down to find all the NIC types in dmesgd and you'll get
nothing at all, because that feature doesn't exist.  bsdstats obviously
needs some TLC, but why reinvent the wheel?

-Alan