This is my first time working with CI Outage service targets. I was able to relate a CI and it's associated Time Entity. Outage calculations seem to be working as expected. The problem is the measurement cycle. According to the documentation (and BMC Support), when you set the lifecycle interval to one month, that month a) starts when you create the service target and b) is actually 720 hours (30 days). I've got a requirement to track availability for calendar months.
Any ideas? Can this be accomplished by having a Service Level Agreement with monthly review periods? It's frustrating because the functionality is exactly what I need if I could specify the measurement period better. -- Chris Danaceau Confidentiality Notice: This email, including attachments, may include non-public, proprietary, confidential or legally privileged information. If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
