Re: Querying scheduled outages via ReST
JohnD Blackburn <[email protected]>
| Newsgroups | gmane.network.opennms.general |
|---|---|
| Message-ID | <DB6PR0602MB29024E7C301E4AC423A3C422CB670@DB6PR0602MB2902.eurprd06.prod.outlook.com> |
The following is added to notifd-configuration/poller-configuration/etc... <outage-calendar>Test-Outage</outage-calendar> <outage-calendar>prd-app01 weeky recycle</outage-calendar> <outage-calendar>prd-app02 weekly recycle</outage-calendar> <outage-calendar>prd-bat01 weekly recycle</outage-calendar> I can grab that info by mining it directly out of the xml files before I push any updates, but it would be much neater if I could query the data via ReST. John Blackburn -----Original Message----- From: David Hustace [mailto:[email protected]] Sent: Wednesday, 20 September 2017 5:51 AM To: DiscussionList List <[email protected]> Subject: Re: [opennms-discuss] Querying scheduled outages via ReST > On Sep 19, 2017, at 02:47, JohnD Blackburn <[email protected]> wrote: > > Is there something that isn’t documented? Or should I be raising an issue for this? I think that the only way that you'll be able to relate outages to notifications is if the event creating outage is also associated with a notification. You'd have to get the eventID from the ReST API of the outage and query the notification's API using that eventID... if that works. Cheers, David David Hustace The OpenNMS Group, Inc. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-discuss mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-discuss