[Bug 1080] New: pmcd result timestamping

[bugzilla-daemon@xxxxxxxxxxx]

Bug ID	1080
Summary	pmcd result timestamping
Product	pcp
Version	unspecified
Hardware	All
OS	Linux
Status	NEW
Severity	major
Priority	P5
Component	pcp
Assignee	pcp@kenj.com.au
Reporter	fche@redhat.com
CC	pcp@oss.sgi.com
Classification	Unclassified

buffalo item

- pcp todo item 14: pmfetch timestamps
  - especially for slightly tardy pmdas, the pmResult timestamp is
    ambiguous: is it at beginning, end, or middle of process?
  - having too-short inter-fetch timestamp intervals can lead to
    crazy-big rate-converted values
  - maybe just confirm/fix pmcd to return beginning-of-operation timestamps
  - apps can also confirm that timestamp is reasonable, by comparing to
    their own clocks around pmFetch()
  - pmlogger could emit diagnostics for violations

Note src/pmcd/src/dofetch.c:530, __pmtimevalNow() is called -after- all
the subsidiary agent fetches are complete.

---

      You are receiving this mail because:

• You are on the CC list for the bug.