From: Les M. <les...@gm...> - 2011-08-25 15:01:46
|
On 8/25/2011 9:04 AM, Duncan Mackintosh wrote: > Cheers Craig, that's about what I was assuming was the case to be honest. The hardest thing I've found to try and get out of REST was 'node availability over last X days' - the db function that calculates this looks at sum(outages)/count(managed services), the latter of which isn't something you can fetch in bulk over REST as it's in the form rest/nodes/<node criteria>/ipinterfaces/. I *could* expose a list of all ip interfaces through REST, though I'm not sure if that's creeping too far. Your thoughts? > > That aside, I needed to make two minor tweaks to the current REST api: making nodeparentid visible on nodes (changing it from @XmlTransient to @XMLIDRef) and adding a page to fetch a list of all known categories. Both seem generic enough to upstream, so I've put them in enhancement ticket NMS-4893. How about a RESTish way to get sample-level data from the jrb's instead of just min/max/avg for a time slice? Even better would be a way to do aggregate math on the samples across a category, but it might be hard to describe the right elements for something like the internet-facing interfaces on a group of routers. The problem is that the sum of the max values of different elements for a time slice larger than a sample won't be the correct max that the total of the group hit at one time - which is often what you need to know. -- Les Mikesell les...@gm... |