Repository navigation
Integration with Nautobot / NetBox ? #1389
Description
Thank you for this excellent Softare 😃.
I'd like to know if there are any Possibilities to integrate NetAlertX with something like Nautobot / NetBox for IP Address Management so that known Devices can automatically be marked as such. Other Fields (e.g. Name, Vendor, Type, Location, Group, ...) could be automatically populated as well 👍.
I'm not currently using Nautobot, but it's on my To-Do List to (hopefully soon) deploy it. I just started using NetAlertX inside an Alpine KVM Virtual Machine running Podman as Root (something which I typically never do but is needed here to access the L2/ARP Network).
Otherwise I would have to write my own Bridge using the API on either Side to e.g. update existing Devices Credentials based on their MAC Address etc.
A quick glance at the Documentation shows that it might be to just to a simple API POST Request using either of:
- https://github.com/jokob-sk/NetAlertX/blob/main/docs/API_DEVICE.md#2-update-device-fields
- https://github.com/jokob-sk/NetAlertX/blob/main/docs/API_DEVICE.md#7-update-a-single-column
Or would I need to use GraphQL ? From past Experiences I found GraphQL to be much more difficult to decipher, probably because I'm not very experienced with it.
Activity
jokob-sk commentedon Jan 7, 2026
Hi,
It should be possible, depending on the intended source of truth.
I would suggest to look into plugins first though - it might be better to implement this as an ingestion plugin from the mentioned tools:
https://jokob-sk.github.io/NetAlertX/PLUGINS_DEV/
The advantage of a plugin approach is that you can see ingested data, the system handles the UI, settings and execution of it. The disadvantage is you currently can't have authoritative plugins that overwrite existing entries. So if a device exists a plugin is not allowed to overwrite existing fields if that field has valid (invalid data would e.g. be
(unknown)) data.Happy to accept a PR for a plugin.
luckylinux commentedon Jan 8, 2026
Let me see if I understand the Limitations correctly 😃.
A Plugin CAN:
But it CANNOT:
Is this a correct Understanding of their Capabilities and Limitations ?
Nautobot / Netbox are typically used as the "Single Source of Truth" so they are supposed to be Authoritative, at least from my Understanding.
This would mean that if an Item is updated on Nautobot / Netbox (e.g.
Hostnameis changed), it will NOT be able to be updated in NetAlertX automatically, correct ?jokob-sk commentedon Jan 8, 2026
Yes, your understanding is correct, however I do plan to implement authoritative plugin controls in the future.
jokob-sk commentedon Jan 20, 2026
Should be possible once this is merged: #1435
jokob-sk commentedon Oct 2, 2026
Hi @luckylinux - would you be interested to create a plugin for that as it's now possible?
luckylinux commentedon Oct 2, 2026
Hi @jokob-sk: I kinda disconnected from the Project.
To be honest I wasn't particularly happy that the entire Thing that I contributed for the Reverse Proxy & Authentik IdP SSO got removed a few Commits later. I get it that the People driving the Project have their own Priorities and surely you are more aware of the Big Picture of what is going on. I just don't like investing Time building something only to have it destroyed/removed shortly after. I am not criticizing you directly, it's just the way it is. It was most likely a bit of a messy moment back then and lack of Coordination.
jokob-sk commentedon Oct 2, 2026
I understand where you’re coming from, and as you said, the coordination could have been much better. Sometimes it’s difficult to balance what should be included and maintained going forward, keeping new contributors engaged, and making decisions that won’t create too much maintenance in the long term.
In this case, I probably leaned too far towards allowing content that I wasn’t fully across, so I can understand how frustrating it must have been to put time into something only for it to be removed shortly afterwards.
I completely understand your decision to step back from the project, and I appreciate the contribution you made. Thank you. Hopefully I’ll be able to keep maintaining the project for a while, in case you ever decide to contribute again. 🙏
luckylinux commentedon Oct 2, 2026
With the Afterthought and what I learned since then, your Decision might have been correct, if now both the WebUI and the API Endpoints were under the same Port. Authentik Outpost Proxy would have prevented the API Endpoint to be used since it does NOT support unattended Tools. Both the Coordination and Communication could have been better though, agreed.
I discovered that Issue when trying to get local LLMs working (
ollama/llama.cppwith LiteLLM).Fortunately though, while Authentik Outpost Proxy does NOT support unattended Tools,
oauth2-proxydoes, while at the same Time working correctly with the Browser.I described how I achieved it in a LiteLLM Issue on their Issue Tracker, though the basic Operating Principle is the same for every Application.
jokob-sk commentedon Oct 2, 2026
That makes sense, and thanks for explaining the above. It sounds like
oauth2-proxyended up being a good solution for supporting unattended API/tool access while still working correctly in the browser - good to know.Even if the direction ultimately made sense, I could have communicated the change and handled the transition much better.
Thanks again for sharing this - it’s good to know there’s a workable approach for the local LLM and API use case as well.
luckylinux commentedon Oct 3, 2026
It's for every unattended/browser Tool that it can be used actually 😉.
If interested that's something I can just copy-paste into a separate Repository (I don't want to cross-link the Issue because, well, they don't really have anything to do with each other).
jokob-sk commentedon Oct 3, 2026
Ah, got it 😉 That sounds useful. If you’re happy to put it in a separate repository, feel free to send it through - I’d be interested to have a look.
luckylinux commentedon Oct 4, 2026
@jokob-sk: https://github.com/luckylinux/demo-oauth2-proxy
oauth2-proxyis not the most Intuitive Piece of Software and, as soon as you need to switch to some Advanced Configuration (in my Case to customize and map custom HTTP Headers), then you need to use that Alpha Configuration Format (seeadvancedSubfolder). Then it's a bit half-half which Configuration needs to be put in Environment Variables or in thatalpha-config.yml.In most Cases I use the
simpleFormat though (I thinklitellmis the only one where I useadvanced).jokob-sk commentedon Oct 4, 2026
Thanks for sharing - will have a closer look in the next few days! :)