Re: Querying scheduled outages via ReST
JohnD Blackburn <[email protected]>
| Newsgroups | gmane.network.opennms.general |
|---|---|
| Message-ID | <DB6PR0602MB2902F46CA363EDA34BA8BD1ACB600@DB6PR0602MB2902.eurprd06.prod.outlook.com> |
That’s what I'm wanting to do, to get the current list of poller/collectd/threshd package names currently linked to an outage so that I CAN re-create the entries via ReST. But I need to be able to get that list via ReST before I can use ReST to re-create them. This is a configuration deployment issue. If someone has created a scheduled outage in the production OpenNMS server, then deploying the latest notifications.xml/collectd-configuration.xml/etc from the UAT OpenNMS server removes the association of the packages to the outages. So I'd like to be able to query the current associations via ReST before I push the update so that I can re-establish the associations after the update. John Blackburn -----Original Message----- From: Roskens, Ronald [mailto:[email protected]] Sent: Wednesday, 20 September 2017 7:46 AM To: DiscussionList List <[email protected]> Subject: Re: [opennms-discuss] Querying scheduled outages via ReST If you know the outage name and the poller/collectd/threshd package names, you can add the outage-calendar entries via REST. There isn't a way via REST to query what packages are there in the configurations through. There are various open JIRA issues to enhance OpenNMS to allow this. (NMS-8698, NMS-9150, NMS-9151, NMS-9152, NMS-9153, NMS-9154). Ron > -----Original Message----- > From: David Hustace [mailto:[email protected]] > Sent: Tuesday, September 19, 2017 2:51 PM > To: DiscussionList List > 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. ---------------------------------------------------------------------- This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you. ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ 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