[PDB Tech] Using the API for integration into LibreNMS
Martin J. Levy
mahtin at mahtin.com
Tue Mar 14 21:40:52 PDT 2017
> ... that will equate to a large number of api hits per install so could
Arnold's response about the multi ASN query is worth doing.
I would also point out that there's always other options.
1) Do a "sync" and have a local copy of the database to query (we do this
at Cloudflare for our peering tools and I know that others do the same).
2) Keep a cached copy of the data for any object so that if you see the
same ASN more than once you will have what you already need. Note that
keeping data cached for X days is pretty safe; where X is your choosing.
3) Throw caution to the wind and simply say "If we are a legit user of the
data; then PDB should be built with the capability to handle the populace
of users in the world".
I actually like #3 as this sounds like a pretty legit user of the data;
plus I know a pretty cool CDN that could help PDB handle the added load! :)
On Tue, Mar 14, 2017 at 5:01 PM, Arnold Nipper <arnold at nipper.de> wrote:
> On 14.03.2017 23:43, Neil Lathwood wrote:
> > PDB is built to be used. Go call the /asn/nnnn endpoint to get the
> > name. BTW: Keep in mind that the name of a network may not be the
> > same on PDB as it is via whois on an RIR (or RADB). The name of a
> > network used for peering is sometimes "unique".
> > Thanks for the reply Martin, this would involve a call for every peer on
> > an Exchange - that will equate to a large number of api hits per install
> > so could mount up.
> If you are worried about the number of api calls try this. Build a list
> of peers asn1, asn2, ... asnn and then call
> That way it's only one call. Or simply do
> and look for the (asn,name) pair in the answer.
> Pdb-tech mailing list
> Pdb-tech at lists.peeringdb.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pdb-tech