Announcing the NetBox Advocates Program

1 minute read

Are you a NetBox power user? Maybe you’ve even built a plugin or custom script? Would you like to be more involved in feature development and roadmap planning for NetBox? To better enable community members like you to have a direct impact on NetBox’s development, today we’re launching the NetBox Advocates Program!

What does it mean to be a NetBox advocate?

  • We’ll occasionally reach out (via email) for feedback on specific new or planned NetBox features. For example, we may ask for feedback on the plugins development experience, or which of several potential new features you’d prefer to see first. This feedback will help guide NetBox’s long-term development.

  • You may be offered access to pre-release instances of NetBox or other tools for evaluation and feedback.

  • You’ll be able to leverage our community Sentry service for error reporting and correlation. We’ll proactively reach out to advocates who opt to enable this service regarding any new errors we detect. We may ask if you can assist with reproducing the error to help develop a fix, or point you to a potential fix.

  • Your organization’s logo will optionally be published in our list of advocates.

And this is just the beginning! We fully expect the importance of the advocates program to grow as the NetBox ecosystem continues to expand.

Register here to get started!


Error Logging with Sentry

1 minute read

One of the challenges that comes with developing open source software is getting reliable and detailed bug reports from users in the wild. Because NetBox is generally self-hosted and has no phone-home function, we don’t have any direct access to deployments other than what we (the maintainers) deploy ourselves. But there’s a new feature in NetBox v3.2.3 that I think can really help us out: Sentry intgeration.

Enabling error reporting via Sentry allows us to collect and analyze exceptions and other errors as they happen, rather than having to wait for bug reports submitted by end users. It won’t capture all bugs, of course, but it will alert us to the more severe issues. Sentry reports include a full stack trace, which is often needed to determine just where a bug exists, but no end user-identifiable information or confidential data.

To enable Sentry integration, simply turn on the SENTRY_ENABLED configuration parameter and restart NetBox:

SENTRY_ENABLED = True

NetBox will begin generating error reports and sending them to our centralized ingestor. One of the biggest benefits of this community-powered arrangement is that we’ll be able to correlate bugs by software release, operating system, and other deployment attributes.

An example Sentry error report

Of course, it’s possible to use your own Sentry ingestor too: You’ll just need to define your custom DSN:

SENTRY_ENABLED = True
SENTRY_DSN = "https://examplePublicKey@o0.ingest.sentry.io/0"

You can find more detail on Sentry configuration in the NetBox documentation.


NetBox v3.2.3 Released

1 minute read

NetBox v3.2.3 is now available on GitHub!

Enhancements

  • #8805 - Add “mixed” option for device airflow indication
  • #8894 - Include full names when listing users
  • #8998 - Enable filtering racks & reservations by site group
  • #9122 - Introduce clearcache management command & clear cache during upgrade
  • #9221 - Add definition list support for Markdown
  • #9260 - Apply user preferences to tables under object detail views
  • #9278 - Linkify device types count under manufacturers list
  • #9280 - Allow adopting existing components when installing a module
  • #9314 - Add device and VM filters for FHRP group assignments
  • #9340 - Introduce support for error reporting via Sentry
  • #9343 - Add Ubiquiti SmartPower power outlet type

Bug Fixes

  • #9190 - Prevent exception when attempting to instantiate module components which already exist on the parent device
  • #9267 - Remove invalid entry in IP address role choices
  • #9296 - Improve Markdown link sanitization
  • #9306 - Include VC master interfaces when selecting a LAG/bridge for a VC member interface
  • #9311 - Permit creating contact assignment without a priority via the REST API
  • #9313 - Remove HTML code from CSV output of many-to-many relationships
  • #9330 - Add missing module_type field to REST API serializers for modular device component templates

NetBox v3.2.2 Released

1 minute read

NetBox v3.2.2 is now available on GitHub!

Enhancements

  • #9060 - Add device type filters for device bays, module bays, and inventory items
  • #9152 - Annotate related object type under custom field view
  • #9192 - Add Ubiquiti SmartPower connector type
  • #9214 - Linkify cluster counts in cluster type & group tables

Bug Fixes

  • #4264 - Treat 0th IP as unusable for IPv6 prefixes (excluding /127s)
  • #8941 - Fix dynamic dropdown behavior when browser is zoomed
  • #8959 - Prevent exception when refreshing scripts list (avoid race condition)
  • #9132 - Limit location options by selected site when creating a wireless link
  • #9133 - Upgrade script should require Python 3.8 or later
  • #9138 - Avoid inadvertent form submission when utilizing quick search field on object lists
  • #9151 - Child prefix counts not annotated on aggregates list under RIR view
  • #9156 - Fix loading UserConfig data from fixtures
  • #9158 - Do not list tags field for CSV forms which do not support tag assignment
  • #9194 - Support position assignment when add module bays to multiple devices
  • #9206 - Show header for comments field under module & module type creation views
  • #9222 - Fix circuit ID display under cable view
  • #9227 - Fix related object assignment when recording change record for interfaces

NS1 is Hiring a NetBox Developer

1 minute read

NS1 is hiring a software to help develop our commercial NetBox Cloud product as well as the open source NetBox project. This candidate will work alongside myself and the rest of our NetBox team here at NS1, and will routinely engage with the NetBox maintainers and community. From the posting:

You will:

  • Help lead the development of NetBox Cloud’s roadmap.
  • Engage in product and roadmap planning discussions.
  • Contribute to documentation and supporting tooling for both the NetBox community and NS1’s NetBox offerings.
  • Work closely with NS1’s NetBox-focused SREs.
  • Support the open source NetBox project and assist in delivering its roadmap.
  • Seek new ways to deliver the best possible user experience for NetBox users.
  • Become an active member of the NetBox open source community.

Ideally, you’ll bring:

  • Proficiency in full stack Python development with a particular focus on development for web applications using Django
  • Solid experience with RESTful APIs and JSON
  • Experience in enterprise network architecture and operations
  • Prior engagement with NetBox as a user, operator, or open source contributor
  • Familiarity with software development best practices, including revision control and documentation
  • Excellent communication skills (written and verbal) and comfort engaging with prospective and current customers to collaborate and solve problems
  • Ability to perform well as part of a distributed team
  • Extra kudos for familiarity with:
    • Experience coaching junior software engineers
    • Open source software and engagement with open source development practices
    • Core network engineering concepts
    • One or more commercial DDI solutions
    • TypeScript development experience
    • Ansible, Salt, or similar configuration management software
    • Tools in the modern DevOps toolkit
    • Cloud infrastructure (AWS, GCP, Azure)

This position is available for full-time remote work, to candidates in the US, UK, and Ireland. You can learn more about this role and apply on NS1’s careers site.