Leo Kirchner

Some of this is addressed with #308

#97 is another way to solve your specific use case, although I don't think this invalidates API access to the logs entirely.

Further notes: - Should probably use [Prometheus SD](https://prometheus.io/docs/prometheus/latest/http_sd/) to make the new set of endpoints discoverable easily - For backwards compatibility, it will be good to keep current `/metrics` around,...

We have this now which is basically the white/blacklisting: https://github.com/nautobot/nautobot/pull/5493

Thanks for submitting! Can you provide a full model and adapter to reference?

If you can give me something I can run as is then I can reproduce the issue much quicker, i.e. flesh out `# GETS IP DATA AND ASSIGNS TO VARIABLES`...

This looks good, thanks.

Should look at pushing the entire logic into `Endpoint`, allowing `limit` and `offset` in kwargs instead. Keeps the API for the end user the same but should be cleaner internally....

Hi, thanks for the submission! As part of #292 I looked at cables, too. One important thing to note here is that updating the terminations of a cable is not...

Some documentation for job testing will be found in the Nautobot docs with 1.3 and also https://github.com/nautobot/nautobot/pull/1617