Hello! I'd like to request that the following two issues be brought up onShould be no problem, IMHO a "good thing" for other scenarios too. At worst it adds two extra tags.
the next call.
As one of the main designers of the Advisor, I have been spending a good
deal of time figuring out what we need to do in order to use the current
NM-WG schema. Currently, we would require some changes to the schema in
order to use it at all.
The Advisor is a very flexible framework in that whoever installs our
Performance Data Collector, they can plug in any tool they wish to gather
metrics. We do not have absolute control over what metrics a PDC will
provide. Therefore, in order for us to use the current schema we would
need the following changes:
1) The ability to return more then one metric in a single xml
envelope: We need the ability to return all metrics since we do
not necessarily know metrics are available on our measurement
point.
Sounds reasonable. I need to look back through the schema and figure out a clean and simple way to accommodate this. Of course, there wouldn't be any way to check that any parameters reported in the result made sense for a generic characteristic. But the result section is mostly generic, anyways, so that should work OK.2) A generic container for metrics: I noticed that the string NetworkCharacteristic was removed and there are bunch of predefined metrics in the schema. What we need (for things such as Web100) is the ability to return anything we want, and its value.
I'm willing to discuss these more in detail if needed... or if you have solutions to these problems, let me know. Thanks, Tanya Brethour NLANR/DAST