| It would be nice as part of a 'manage the manager' feature, to be able
to ask about all recording going on - even if that means building a
table somewhere everytime a entity record is started. The output would
show record status, entity, partition, domain, attributes, etc... There
have been times that my export files were getting larger, but I
couldn't find out why - without walking the tree for my entities.
bill
|
|
from .0:
> 1) When I look at the "Last export time = " item, it doesn't
> show the last export time, but the time before last. Not very
> important, but IT IS WRONG.
The meaning of the "Last export time" is "time when Exporter FM
does mcc_calls to obtain requested data" but NOT "time when these
data is written in the data base".
"Last export time" is updated when all data for the same data base
row are returned. Due to the the nature of statistics
attributes they are returned with delay in duration (export
period).
|<---export period---->|<---export period---->|
-x----------------------x----------------------x---->time
T1 T2 T3
|<- Last Export Time->|
| = T1 |
v v
data T1 are data T2 are
returned returned
from .0:
> SHOW EXPORT NODE4 *, goes tru every single registered node and
> tells me if it has an EXPORT or not. But it does not show if
> the one of the node's children does have an export, or if the
> export target file is not the default "MCC_EXPORT.RDB", etc...
From SRM 5.3 "Entity Wildcarting":
"The PM will attempt to enumerate all global entity instance
wildcards entered as entity in a command, then converting the
user command into one call per global entity."
So the Exporter FM does not see "NODE4 *" you entered in the
command. If you try SHOW EXPORT NODE4 <node_name> LINE *
you will see exporting requests for all lines of the specified
node.
from .0:
> What is needed, is for the command not to go tru the hole entity
> registration database. But rather go to the MIR, and directly
> extract the KNOWN EXPORTS and give them to the user.
from .1:
> It would be nice as part of a 'manage the manager' feature, to be able
> to ask about all recording going on - even if that means building a
> table somewhere everytime a entity record is started. The output would
> show record status, entity, partition, domain, attributes, etc...
On our list we have function you are asking for. I call it "List Exporting"
and "List Recording". This function will return the same information
as "Show Exporting/Show Recording" but only for entities those
exporting/recording request exists. This command will accept a target
entity as an argument (not as entity). This allows global entity
wildcarding be passed to the Exporter/Historian FM.
The user will be able to set up different filters, for example,
state = ACTIVE. In addition to this the user will be able to set up
different output formats.
> 3) I have not checked if the SHOW RECORD command has similar
> "features", but if so, they too should be fixed.
Historian FM records information on per partition basis. Please note
that statistics attribute partition can NOT be recorded. The following
schema illustrates the "Last Polling Time" parameter:
|<---polling period--->|<---polling period--->|
-x----------------------x----------------------x---->time
T1 T2 T3
|<-Last Polling Time ->|
| = T1 |
v v
data T1 are data T2 are
returned returned
Global entity wildcard expansion is common for all FMs.
Sam
|