Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Web Interface

    Description

      It would be cool if observium gets a netbox integration.

      Netbox is an IPAM and DCIM.

      https://github.com/netbox-community/netbox

       

      So i decided to include some quick and dirty code to display a navbar tab with a link to my netbox instance.

       

       

      You also need some config-variables:
      // Netbox
      $config['netbox_enable'] = 1;
      $config['netbox_api_token'] = "xxxxxxxx";
      $config['netbox_api_base_url'] = "http://netbox.xxxxx.xxxx/api/";

      I attached a patch. You can use and implement it if you find this cool, too!

       

      I don't know how to handle the icons - so i used the "info" icon which is not cool. And i did not put much effort into exception catching, because i dont know what you think about it.

       

      You could also implement other things, like a sub page with details requested via the API, so that you don't need to leave the observium page to get all those information.

       

      Attachments

        1. image-2021-01-30-00-08-36-385.png
          330 kB
          Florian Meyer
        2. netbox.ico
          1 kB
          Florian Meyer
        3. netbox.patch
          2 kB
          Florian Meyer

        Activity

          [OBS-3629] Support for Netbox IPAM/DCIM

          oh, and handling icons is the biggest shit show in web, no good solutions, everything sucks.

          adama Adam Armstrong added a comment - oh, and handling icons is the biggest shit show in web, no good solutions, everything sucks.

          This is probably better done during discovery, storying the netbox device id in a device attribute, and then showing the navbar item if that attribute exists, you absolutely do not want the navigation generation reliant on an external application. if the application is not there, the web ui would become practically unusable.

          it's also probably a bad idea to make a navbar entry for this, as space on that bar is very limited, and we already hit the max in devices with routing/vlans/etc.

          If you want to make a specific netbox page, it doesn't matter so much that it's talking to the api, since it'll only be affected on that page. we don't so much mind at that point.

          adama Adam Armstrong added a comment - This is probably better done during discovery, storying the netbox device id in a device attribute, and then showing the navbar item if that attribute exists, you absolutely do not want the navigation generation reliant on an external application. if the application is not there, the web ui would become practically unusable. it's also probably a bad idea to make a navbar entry for this, as space on that bar is very limited, and we already hit the max in devices with routing/vlans/etc. If you want to make a specific netbox page, it doesn't matter so much that it's talking to the api, since it'll only be affected on that page. we don't so much mind at that point.

          People

            landy Mike Stupalov
            FloMeyer Florian Meyer
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: