[Oslc-pm] monitoring agent availability status
Julianne Bielski
bielsk at us.ibm.com
Tue Aug 28 14:19:09 EDT 2012
For Computer Systems that are also Performance Monitoring Records, the
workgroup is looking at providing monitor availability status. We believe
that knowing that expected performance monitoring is occurring is a Best
Practice metric.
We're considering describing this information this way so far:
<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:ems="http://open-services.net/ns/ems#"
xmlns:pm="http://open-services.net/ns/perfmon#"
xmlns:dbpedia="http://dbpedia.org"
xmlns:qudt="http://data.nasa.gov.qudt/owl/qudt#"
xmlns:foaf="http://xmlns.com/foaf/0.1/">
<rdf:Description rdf:about="
http://example.org/computerSystemRecord001#myMonitoringAgent">
<rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
<dcterms:title>
Log File Monitoring Agent
</dcterms:title>
<ems:metric rdf:resource="pm:AgentAvailabilityStatus"/>
<ems:Value rdf:datatype="http://www.w3.org/2001/XMLSchema#string
">Not
Running
</ems:Value>
<ems:unitOfMeasure rdf:resource="qudt:Dimensionless"/>
</rdf:Description>
</rdf:RDF>
Notice the pm:AgentAvailabilityStatus metric with literal value Not
Running
Does this seem accurate?
Here are other values that could also be provided:
Unknown (0), Not_found (1), Stopped (2), Start_Pending (3), Running (4),
Manually_Stopped (5), Stop_Pending (6), Not_Configured (7).
-- Regards,
Julianne Bielski, STSM
ITM Core Chief Architect
Tivoli, IBM Software Group
tel: (919) 224-1170 (T/L) 687-1170
e-mail: bielsk at us.ibm.com
"All growth is a leap in the dark, a spontaneous unpremeditated act
without benefit of experience." — Henry Miller
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-pm_open-services.net/attachments/20120828/8d038f8b/attachment-0003.html>
More information about the Oslc-Pm
mailing list