Skip to main content

netbox-opennms-plugin

Provision NetBox devices and virtual machines into OpenNMS Horizon 36 as requisition nodes. NetBox holds the monitoring intent. The plugin renders it into OpenNMS requisitions and imports them over the REST provisioning API.

CI Release License: MIT NetBox 4.6.1+ Python 3.12+ Docs PyPI Downloads

📖 Documentation & contributor guide →

Requisition detail illustration

flowchart LR
  NB[NetBox Devices / VMs] -->|live filter| R[Requisition]
  R -->|Sync job on RQ worker| API[OpenNMS REST provisioning API]
  API --> FS[(Foreign Source + nodes)]

Contents

Features

Feature Description
Filter-based Requisitions A Requisition is one user-named OpenNMS Foreign Source. Its members are a live NetBox filter (role, tag, site, status, custom field, …) over Devices and/or Virtual Machines.
Discovery-driven detectors & policies Classes and parameters are read from your live OpenNMS over REST. A curated preset overlay adds labels and defaults. A freeform class is always accepted.
Per-interface SNMP roles The management IP is the Primary SNMP interface by default. Add more IPs as Primary, Secondary or Not-eligible.
Asset & metadata enrichment Map NetBox inventory to OpenNMS node asset fields. Attach metadata at node, interface or service scope.
Conflict safety An object matched by two Requisitions blocks Sync of both until you resolve it. A node lives in exactly one Foreign Source.
Graded node status A member with no management IP becomes an inventory-only node with a warning, not a silent skip.
Dry run A per-node diff of what a Sync would add, remove or change against the live OpenNMS state.
Background sync Sync and Remove run as NetBox Jobs. A drift reconciler removes Foreign Sources the plugin pushed and no longer governs.

Compatibility

Component Version
NetBox 4.6.1+ verified against
Python 3.12+
OpenNMS Horizon 36

Try it locally

The quickstart/ stack runs a throwaway NetBox (UI and worker) and a disposable OpenNMS Horizon 36. It uses fixed throwaway secrets and is not for production.

  1. Start the stack:

    cd quickstart
    docker compose --profile opennms up -d --wait
    
  2. Seed example Devices, VMs and Requisitions:

    ./seed.sh
    

    Expected output (after the NetBox startup log):

    Seeded:
      sites=3 roles=3 devices=7 vms=3 requisitions=5 overrides=4
    
    Foreign Sources (resolved requisitions):
      netbox.durham.router         rtr-3
      netbox.raleigh.firewall      fw-1
      netbox.raleigh.router        rtr-1, rtr-2, vm-1, vm-2
      netbox.raleigh.switch        sw-1, vm-3
    
    Unmonitored: sw-durham (no requisition) · sw-2 (override excludes it)
    Now open http://localhost:8000/plugins/opennms/sync/ and Sync.
    
  3. Open the Sync Preview at http://localhost:8000/plugins/opennms/sync/ and log in as admin / admin.

  4. Open a Requisition, click Dry run, then Sync to OpenNMS.

  5. Open OpenNMS at http://localhost:8980/opennms (admin / admin) and check the requisition's nodes under the provisioning requisitions page.

  6. Tear the stack down:

    docker compose --profile opennms down -v
    

The full walkthrough is in the Quickstart guide.

Install the plugin

  1. Install the package into NetBox's virtual environment from PyPI:

    /opt/netbox/venv/bin/pip install netbox-opennms-plugin
    
  2. Add netbox_opennms to the existing PLUGINS list in NetBox's configuration.py:

    PLUGINS = [
        # ...your other plugins
        "netbox_opennms",
    ]
    
  3. Set the connection in PLUGINS_CONFIG. See Configure OpenNMS servers.

  4. Apply the migrations:

    /opt/netbox/venv/bin/python /opt/netbox/netbox/manage.py migrate netbox_opennms
    
  5. Restart NetBox and its RQ worker:

    sudo systemctl restart netbox netbox-rq
    
  6. Confirm the migrations are applied:

    /opt/netbox/venv/bin/python /opt/netbox/netbox/manage.py showmigrations netbox_opennms
    

    Expected output:

    netbox_opennms
     [X] 0001_initial
     [X] 0002_requisition_redesign
     [X] 0003_deployedforeignsource
     [X] 0004_remove_requisition_priority
     [X] 0005_remove_monitoringoverride_additional_ips_and_more
     [X] 0006_assetmapping_metadataentry
     [X] 0007_opennmsserver
    

Prepare OpenNMS

The plugin writes requisitions. It does not configure OpenNMS polling.

  • Provisioning account. Give each server's username a role that can read and write requisitions and trigger imports.
  • Poller packages. OpenNMS polls a discovered service only if a poller package covers it. Make sure poller-configuration.xml covers the services your detectors discover and the Requisition's declared services.
  • Minions. A node in a location other than Default is polled only if a Minion is registered at that location. The plugin warns when a location is unknown to OpenNMS but cannot create it.

Configure OpenNMS servers

The plugin can provision several OpenNMS servers. Each Requisition targets exactly one server. Two server rows must not point at the same OpenNMS instance, because Foreign Source names are global on an instance. The plugin rejects a server whose URL matches another server's, ignoring a trailing slash and the case of the scheme and host. A provisioned entry that points at the same OpenNMS as another server is skipped with a warning. Its row is neither created nor updated. A provisioned entry without url, username and password is also skipped with a warning, and no row appears for it. A server comes from one of two origins:

  • Provisioned. Declared in PLUGINS_CONFIG in NetBox's configuration.py. The UI shows it as Managed by configuration and refuses edits and deletes. Its credentials are read from the configuration at runtime and never reach the database.
  • Local. Created under Plugins → NetBox OpenNMS → OpenNMS Servers or through the REST API. Every field is editable. The password and headers are stored Fernet-encrypted.

Declare provisioned servers in the servers mapping, keyed by name:

PLUGINS_CONFIG = {
    "netbox_opennms": {
        "servers": {
            "prod": {
                "url": "https://opennms.example.org/opennms",
                "username": "provision-svc",
                "password": "********",  # load from your secrets mechanism
                "default_location": "",
                "headers": {},
            },
        },
        "import_mode": "false",
        "reconcile_orphans": "true",
    },
}

headers are extra HTTP headers sent with every request, for a server behind an auth proxy. Basic auth is always sent too.

A single server can still use the flat keys opennms_url, opennms_username, opennms_password and default_location. They are the single-server shorthand for servers["default"]. When a servers.default entry exists, the flat keys are ignored.

Provisioned rows are created or updated on every migrate and when a user with change_opennmsserver opens the server list. The URL and credentials are always read from the configuration. A changed default_location applies after the next update. A local row with the same name as a configured server is taken over: it becomes provisioned and its stored credentials are cleared. When you remove a server from the configuration, its row stays, because Requisitions may still point at it. The row shows Missing from configuration and cannot sync. Re-add it to the configuration, or edit it and enter credentials to convert it to a local server. A server with Requisitions cannot be deleted.

Local credentials are encrypted with a key derived from NetBox's SECRET_KEY. Set credentials_key to use a dedicated Fernet key instead:

python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().decode())"

Changing credentials_key, or SECRET_KEY while credentials_key is empty, makes the stored credentials unreadable. They are not re-encrypted with the new key. Setting credentials_key for the first time counts as a change. Affected servers show Credentials need re-entering in the server list. Open each one and enter the password and headers again.

To test a server, open its detail page and click Test connection. The test needs the netbox_opennms.view_opennmsserver permission and stores nothing.

The netbox_opennms.add_opennmsserver and netbox_opennms.change_opennmsserver permissions let a user point the stored credentials at any host. Grant them to administrators only.

Monitoring on several servers. An object matched by two Requisitions on the same server is a conflict, as described in Architecture. Matches on different servers are independent, so a Device can be a node on production and on staging at once. A Monitoring Override applies on every server. Exclude removes the object from all servers, and the management IP, interfaces, services and location are the same on each. To leave an object out of one server only, narrow that server's Requisition filter.

Upgrade. When Requisitions already exist, migration 0007_opennmsserver creates one provisioned server and points all of them at it. With opennms_url set, that server is named default. With no opennms_url and exactly one servers entry, it is that entry. With several servers entries and no opennms_url, the server is also named default. Name one entry default so it receives the existing Requisitions. Otherwise the migrated default row has no URL and shows as missing until you repoint the Requisitions. Keeping the flat keys for the upgrade deploy avoids this too. When you later switch from the flat keys to the servers mapping, name the entry for that server default. The migrated default row then reads its credentials from the new entry.

All settings are listed in Settings.

Run the sync worker

Start a NetBox RQ worker on the default queue:

/opt/netbox/venv/bin/python /opt/netbox/netbox/manage.py rqworker

Sync, Remove and the drift reconciler run as NetBox background Jobs on that worker. Without a worker, the Requisition and Sync Preview pages show a warning and jobs stay pending. An OpenNMS 202 ACCEPTED is reported as submitted for import, never as provisioned. Each Device/VM detail page shows its last sync state, one row per server. See Sync states.

Deploy on Kubernetes

The netbox-community/netbox chart only enables plugins that are already installed in the image. Bake the plugin into a custom image. Mounting a plugin into the container at runtime is not supported (see netbox-docker PR #1071).

  1. Build and push an image with the plugin. Match the NetBox base to the chart's appVersion (4.6.1 or later) and pin both versions:

    # Dockerfile
    FROM netboxcommunity/netbox:v4.7.3
    RUN UV_SYSTEM_CERTS=true /usr/local/bin/uv pip install netbox-opennms-plugin==0.1.1
    

    The image ships uv, not pip. UV_SYSTEM_CERTS=true makes uv trust the image's operating-system certificate store, which no longer contains the compromised emSign roots, instead of its own bundle.

    docker build -t registry.example.org/netbox-opennms:v4.7.3-0.1.1 .
    docker push registry.example.org/netbox-opennms:v4.7.3-0.1.1
    

    The pin above is the current release. For an air-gapped build, run make build and COPY the wheel from dist/ instead.

    Installing the plugin also upgrades certifi to a version without the emSign roots, which the plugin's HTTPS client trusts by default. For an image you cannot rebuild yet, set REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt on the NetBox and worker containers so the client uses the operating-system store instead.

  2. Store the OpenNMS password in a Kubernetes Secret. The key name must end in .yaml:

    cat > plugins.yaml <<'EOF'
    PLUGINS_CONFIG:
      netbox_opennms:
        servers:
          prod:
            password: "********"
    EOF
    kubectl create secret generic netbox-opennms --from-file=plugins.yaml
    

    Expected output:

    secret/netbox-opennms created
    

    The chart mounts each extraConfig entry into the NetBox and worker pods and deep-merges it over pluginsConfig, so the Secret only needs servers.prod.password. The URL and username stay in values.yaml. If the Secret is not mounted or merged, the entry has no password and the server is absent from NetBox.

  3. Point the chart at the image, enable the plugin, load the Secret and enable the worker in values.yaml:

    image:
      repository: registry.example.org/netbox-opennms
      tag: v4.7.3-0.1.1
    
    plugins:
      - netbox_opennms
    
    pluginsConfig:
      netbox_opennms:
        servers:
          prod:
            url: "https://opennms.example.org/opennms"
            username: "provision-svc"
            default_location: ""
        import_mode: "false"
        reconcile_orphans: "true"
    
    extraConfig:
      - secret:
          secretName: netbox-opennms
    
    worker:
      enabled: true
    

    Leave the worker's image unset so it runs the same plugin-bearing image. A worker without the plugin deploys fine, but every sync job fails at dequeue with an import error.

  4. Install or upgrade. The NetBox image applies migrations on boot.

    helm repo add netbox https://netbox-community.github.io/netbox-chart/
    helm upgrade --install netbox netbox/netbox -f values.yaml
    kubectl exec deploy/netbox -- /opt/netbox/venv/bin/python /opt/netbox/netbox/manage.py showmigrations netbox_opennms
    

    Expected output: every netbox_opennms migration marked [X], as in Install the plugin.

To upgrade the plugin, rebuild the image with the new version, bump image.tag and run helm upgrade again.

Architecture

A Requisition is one user-named OpenNMS Foreign Source. It owns:

  • a live NetBox filter that selects its member Devices and/or VMs,
  • the detectors and policies OpenNMS runs on its nodes,
  • a set of declared services (for example ICMP, SNMP) that are always present on the node.

Each member's management IP is its NetBox primary IP. OpenNMS discovers further services through the detectors. A per-object Monitoring Override can exclude the object, pin a different management IP, add interfaces with an SNMP role (snmp-primary P/S/N, at most one Primary per node), add or suppress a service, or change the location.

Sync renders the complete foreign-source definition and requisition and imports them. Each Sync replaces the whole requisition, so a re-sync is idempotent and never duplicates a node. Membership is a live query, so a changed Device or VM attribute re-resolves on the next Sync.

Node identity is the pair (Foreign Source, Foreign ID), with Foreign IDs device-{pk} and vm-{pk}. Renaming a Device relabels its node in place. Moving an object to another Requisition changes its Foreign Source, which OpenNMS treats as a new node. The dry run shows such moves before you Sync.

Conflicts. Requisition filters on the same server must be disjoint. An object matched by two or more filters on one server is rendered into none of them. Matches on different servers are not a conflict. Sync of every involved Requisition is blocked and their OpenNMS state stays as last synced. Resolve it by narrowing a filter, for example with a negated parameter ({"role": ["switch"], "tag__n": ["critical"]}), or by excluding the object with an override. Conflicts show on the Requisition page, the Sync Preview, the dry run and the affected Device/VM page. The REST API saves without warning, so check the Sync Preview after automated writes.

Validation. Findings are errors or warnings. Errors block Sync: a filter conflict, a rejected filter (unknown key or no effective constraint) and an invalid resolved location. Warnings do not block. A member with no management IP is a warning: it becomes an inventory-only node with no IP interface and is not actively monitored.

Detector and policy discovery. The editors read classes and parameters from GET /rest/foreignSourcesConfig/{detectors,policies}, the API the OpenNMS UI uses. Plugin-provided detectors appear too. Results are cached for 300 seconds and refreshed at Sync. If OpenNMS is unreachable, the editors fall back to the curated presets for 30 seconds before retrying, and saving still works.

Drift reconciler. Every 60 minutes, a system job checks each server and removes Foreign Sources the plugin pushed but no longer governs: a renamed or deleted Requisition, one moved to another server, or one whose last member left. Ownership is recorded per pushed Foreign Source, so the job never touches requisitions it did not create. Disable it with reconcile_orphans: "false".

Moving a Requisition to another server. Saving a Requisition with a new server in the UI submits a Remove for the copy on the old server. Run a Sync to push it to the new server. When both servers point at the same OpenNMS, nothing is removed and the nodes stay. A server change through the REST API submits no Remove. The hourly reconciler clears the old copy when reconcile_orphans is "true".

Reference

Settings

All values except servers are strings.

Name Type Default Description
servers mapping {} Provisioned servers, keyed by name. Each entry takes url, username, password, default_location and headers. See Configure OpenNMS servers.
credentials_key string "" Optional Fernet key that encrypts local server credentials. Empty derives a key from SECRET_KEY. Generate one with python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().decode())".
opennms_url string "" Single-server shorthand for servers.default. Ignored when a servers.default entry exists. OpenNMS base URL including the context path, for example https://opennms.example.org/opennms.
opennms_username string "" Single-server shorthand for servers.default. REST account with the provisioning role.
opennms_password string "" Single-server shorthand for servers.default. Password for opennms_username. Load it from your secrets mechanism.
default_location string "" Part of the single-server shorthand. It sets the per-server default servers.default.default_location. Monitoring location for Requisitions that set none. Empty means OpenNMS's built-in Default. Each server has its own default location.
import_mode "true" | "false" | "dbonly" "false" rescanExisting value sent with each import. See import_mode values.
reconcile_orphans "true" | "false" "true" Run the hourly drift reconciler. Needs an RQ worker.

import_mode values

Value Effect on import
false Import without rescanning nodes already known to OpenNMS.
true Import and rescan existing nodes (re-run detectors and policies).
dbonly Update the OpenNMS database only. Do not schedule a scan.

Sync states

Shown on each Device/VM detail page, backed by the NetBox Job log.

State Meaning
submitted The job is pending, scheduled or running.
succeeded-accepted The job completed and OpenNMS accepted the import.
removed A Remove completed, or the object is no longer governed or is excluded.
failed The job errored or failed.

UI pages and permissions

Page Menu Permission
OpenNMS Servers Plugins → NetBox OpenNMS. Test connection is a button on each server's detail page. netbox_opennms.view_opennmsserver. add_opennmsserver and change_opennmsserver let a user point stored credentials at any host. Grant them, and delete_opennmsserver, to administrators only.
Requisitions Plugins → NetBox OpenNMS netbox_opennms.view_requisition
Monitoring Overrides Plugins → NetBox OpenNMS netbox_opennms.view_monitoringoverride
Sync Preview Plugins → NetBox OpenNMS netbox_opennms.view_requisition
Dry run Requisition detail page netbox_opennms.view_requisition
Sync to OpenNMS Requisition detail, Dry run netbox_opennms.change_requisition
Sync all Sync Preview netbox_opennms.change_requisition
Duplicate Requisition detail page netbox_opennms.add_requisition
Remove from OpenNMS OpenNMS Sync Status panel on a Device or VM. Sets Exclude on the object's override and removes its node. Clear Exclude and Sync to restore it. netbox_opennms.change_requisition, netbox_opennms.add_monitoringoverride, netbox_opennms.change_monitoringoverride
Remove a Foreign Source POST /plugins/opennms/sync/foreign-source/ with remove set. No button. Needs an existing Requisition of that name. Re-syncs the Requisition and allows an empty result. It clears the Foreign Source only when the Requisition matches no objects. A deleted Requisition's copy is removed by the reconciler. netbox_opennms.change_requisition

Requisition fields

Field Rule
Name Used as the OpenNMS Foreign Source name and in REST URL paths. Unique across all servers, so one Foreign Source name cannot be used on two servers. No whitespace and none of # % & + ? / \ : * ' ".
Object types Devices, Virtual Machines, or both.
Filter NetBox FilterSet parameters, for example {"role": ["switch"], "tag": ["critical"]}. It must constrain every selected object type, so a typo cannot become a fleet-wide catch-all. You can seed it from a NetBox Saved Filter. That is a one-time copy with no live link.

Asset mappings and metadata

Channel Target Rules
Asset mapping A fixed OpenNMS node asset field (OnmsAssetRecord, discovered from /rest/foreignSourcesConfig/assets) The field is validated at save.
Metadata entry A context / key / value triad at node, interface or service scope context defaults to requisition. A custom context must start with X-. Use cf_<name> to read a custom field.

Values resolve per member. An unresolved value is omitted.

REST API

Servers are at /api/plugins/opennms/servers/. The OpenNMS base URL is the address field, because url is the object's self link. password and headers are write-only. origin is read-only. A write to a server managed by configuration returns 403. Requisitions are at /api/plugins/opennms/requisitions/. A new Requisition may omit server only while exactly one server exists.

Troubleshoot

Symptom Cause Fix
Sync jobs stay pending and the Requisition page shows a worker warning No RQ worker is running Start one. See Run the sync worker.
Jobs fail at dequeue with an import error, but the UI works The worker runs an image without the plugin Run the worker from the same image as NetBox.
Sync is blocked A filter conflict, a rejected filter or an invalid location Open the Sync Preview. Narrow the filter, exclude the object or fix the location.
A node shows in OpenNMS but is never polled No poller package covers its services Add the services to poller-configuration.xml.
Nodes in a non-Default location are not polled No Minion is registered at that location Register a Minion at that location.
The detector editor shows presets only OpenNMS was unreachable during editing Click Test connection on the Requisition's server. The editor retries after 30 seconds.
A server shows Missing from configuration and its syncs fail The server was removed from servers in PLUGINS_CONFIG Re-add it to the configuration, or edit it and enter credentials to convert it to a local server.
A local server warns that its credentials cannot be decrypted SECRET_KEY or credentials_key changed Edit the server and re-enter the password and headers.
Pages and jobs that load a local server fail with ImproperlyConfigured naming credentials_key credentials_key is not a valid Fernet key Generate a key with the one-liner in Configure OpenNMS servers and set it.
A node carries a warning and has no IP interface The member has no management IP Set a primary IP in NetBox, pin one with an override, or exclude the object.

Contribute

The contributor guide covers project structure, the dev environment, testing and releases. Everything runs in Docker.

make verify          # ruff lint + full unit suite in a throwaway NetBox stack (the CI gate)
make integration     # live round-trip against a disposable OpenNMS Horizon 36

Before opening a PR:

  • make verify passes.
  • Commits follow Conventional Commits.
  • Commits are signed off (git commit -s) and cryptographically signed. main rejects unsigned commits.
  • Every source file carries an SPDX header.

Support the project

The plugin is MIT-licensed and free to use, with or without a donation. If it saves you time, a one-time donation via GitHub Sponsors or Ko-fi helps fund releases, security fixes, issue triage, and CI infrastructure. Supporters are thanked in SPONSORS.md. Starring the repo, filing good issues, and contributing PRs help just as much.

License

MIT. See LICENSE.

Metadata

Release files for netbox-opennms-plugin 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for netbox-opennms-plugin 0.1.1
File Size Uploaded Provenance Actions
netbox_opennms_plugin-0.1.1.tar.gz 101.7 kB With provenance Details for netbox_opennms_plugin-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for netbox-opennms-plugin 0.1.1
File Interpreter ABI Platform Actions
netbox_opennms_plugin-0.1.1-py3-none-any.whl Python 3 none any Details for netbox_opennms_plugin-0.1.1-py3-none-any.whl

Total release size: 219.5 kB

Release files / netbox_opennms_plugin-0.1.1.tar.gz

Download URL netbox_opennms_plugin-0.1.1.tar.gz
Size 101.7 kB
Tags Source
SHA-256 checksum
How to use checksums
89adf86401e7db6433d6fe9173459e090612b23284a124f2fcf97e14f065629a
BLAKE2b-256 checksum
How to use checksums
15517c4dc134e1dd2247115b31c82dba339f446c8d31f7ee3f98d7724b7ba0e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

Release files / netbox_opennms_plugin-0.1.1-py3-none-any.whl

Download URL netbox_opennms_plugin-0.1.1-py3-none-any.whl
Size 117.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
20a244189ccfef003f7eccd858db7cad1ed63437a7fd81fa0425f0f42984cfda
BLAKE2b-256 checksum
How to use checksums
289c0e480992b0c745b31969ff61ca3b2297dc53f4f46a15084a3b98059eca99
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

Security for netbox-opennms-plugin 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for netbox_opennms_plugin-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page