OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [wsdm] Issue on mows metrics


I agree we should resolve this before 1.0. Shall I add this to our agenda Thursday?

It only has to process the metadata document, which, unfortunately for WSDM 1.0, is a little vague for 1.0.

So lets look at the usage of this information ...

Managers or consumers of metrics typically poll for metrics they are processing. When they find metrics, or someone tells them the
metric name, they will need to look in the metadata document to understand metadata about the metric. They typically do this once for a metric that they are going to poll or subscribe to.

At runtime, when they get the value, on. they need to already understand the type information. They don't need all this type information on every request. There's been some experience (with WBEM) on scalability of implementations that pass around a lot of metadata with value data and I think we'd do well to learn from theirs.

We also need to be consistent in our approach for metadata, we really don't want to scatter it around... even though its tempting for 1.0 given the state of metadata.

Heather Kreger
STSM, Web Services Lead Architect for SWG Emerging Technologies
Author of "Java and JMX: Building Manageable Systems"
kreger@us.ibm.com
919-543-3211 (t/l 441) cell:919-496-9572

Inactive hide details for "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>"Sedukhin, Igor S" <Igor.Sedukhin@ca.com>


          "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>

          11/01/2004 06:53 PM


To

"Fred Maciel" <Fred.Maciel@hds.com>, <wsdm@lists.oasis-open.org>

cc


Subject

RE: [wsdm] Issue on mows metrics

Since such things are now metadata on the metrics, I don't even know how
to deal with them in MOWS. That is the implementer of a web service
endpoint is supposed to publish a metadata documnt which will include
such information.

And another point is that either of those counters could be SinceReset
or Interval. Implementation decides how to expose one.

I actually liked it when these were attributes of the element. I don't
even care that they have to be included with every response. It was easy
to implement and easy to use. Now, we can't even implement manageable
web services because we should look in fifty different places to
understand that the returned metric value is Interval or SinceReset...

So this is the issue we need to close before 1.0.


-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749


-----Original Message-----
From: Fred Maciel [mailto:Fred.Maciel@hds.com]
Sent: Monday, November 01, 2004 5:13 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] Issue on mows metrics

Hi Igor (et al)

Everybody seems to agree that there are no Interval metrics in the
MOWS spec, however, the spec does not specify if the metrics are
Interval, PointInTime or SinceReset. (Igor: that's the issue I told you
about last week. Heather: could you add it to the issues list?).

Regards,

Fred Maciel.

To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou
p.php.



To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.

GIF image



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]