Re: 'Inter-Tables indexing' and perl

On Thu, 2005-10-13 at 12:17 +0200, Turbo Fredriksson wrote:
> > Basic rule - all objects in a given table must use
> > exactly the same indexing structure.  If the indexing
> > is different, that means a different table.
> 
> Is there any way I can modify the index in such a way
> that only need one table?

By only having one job on each system :-)

But seriously - no.
If you need to report information about one or more "foo"
things, each of which can have one or more "bar" things,
then you need two tables:

    fooTable  [indexed by fooIndex]
and barTable  [indexes by fooIndex, barIndex]



>  Making more than one table
> for that will complicate the next table:


> Here, the statsTable is in the format:
> 
> OID_BASE.statsTable.statsEntry.CounterType.ClientID.JobJame.jobID
> 
> 
> There's an 'infinite' number of Job ID's and corresponding
> counters... Making 'infinite' number of tables will be...
> UGGLY! :)

It's OK - you won't need an infinite number of tables!
(just an infinite number of rows)

I just to check a few details.
Are the statistics associated with a particular system,
or an individual job?  (Or both?)  And is the list of
statistics fixed, or variable?



> In LDAP (which I now know better than SQL),
> I would have written the whole thing as:
> ----- s n i p -----
> +- client1
>    +- Client1_System
>       +- Client1_System.2005-09-13_01.05.06
>          +- [start date]
>          +- [end date]
>          +- [duration]
>          +- [files]
>          +- [bytes]
>       +- Client1_System.2005-09-14_01.05.06
>          +- [start date]
>          +- [end date]
>          +- [duration]
>          +- [files]
>          +- [bytes]
> [etc, etc for each client, each job name and each job ID]

So for each client you have the same five statistics - yes?

That would be represented in SNMP using a table

	clientSystemStatsTable

with five columns  (cssStartDate, cssEndDate, cssDuration,
cssFiles, cssBytes), and indexed by the same object used
to index the main clientSystemTable


If these (or other) statistics are actually associated with
a particular job, then the equivalent clientJobStatsTable
would be indexed by a (clientSystemIndex, clientJobIndex)
pair - exactly as for the main clientJobTable.

These tables are effectively "parallel" to the main configuration
information.  For every row in the system (or job) table, there'd
be a corresponding row in the systemStats (jobStats) table.

(Things get a little more complex if the list of statistics can
vary, but it's still basically just one table in each case).

Dave


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users