{"schema_version":1,"metadata":{"branch":"current","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:41.004595+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/sqlports-7.55.tgz","source_sha256":"fcdbba1b9df747882aa9bab4af20ebec8dac10655069c90f1cd4145c06e1235e","package_count":12031,"source_kind":"sqlports"},"package":{"name":"nsca-ng-client-1.7","path":"net/nagios/nsca-ng,-client","url":"/packages/current/net/nagios/nsca-ng,-client/","comment":"client to send passive check results to Nagios/Icinga","homepage":"https://www.nsca-ng.org/","maintainer":"The OpenBSD ports mailing-list <ports@openbsd.org>","description":"NSCA-ng provides a client-server pair which makes the Nagios command file\naccessible to remote systems. This allows for submitting passive check\nresults, downtimes, and many other commands to Nagios or compatible\nmonitoring solutions. The submitted data is queued by the NSCA-ng\nserver if Nagios goes down. Multiple check results or commands can be\nsubmitted in one go, and multiline plugin output is fully supported.\nNSCA-ng uses TLS encryption and shared-secret authentication with\nper-client passwords, as well as fine-grained authorization control.\n\nThis package contains the NSCA-ng client (\"send_nsca\"), which accepts\nall input, command line arguments, and configuration files accepted\nby the send_nsca binary provided with the original NSCA package.\n\nNSCA clients cannot talk to NSCA-ng servers (nor vice versa), but NSCA\nand NSCA-ng servers can happily run side by side.\n","package_architecture":"amd64","stem":"nsca-ng-client","readme":null,"dependencies":[{"path":"devel/libev","type":"library","package_spec":"","url":"/packages/current/devel/libev/"},{"path":"security/openssl/3.5","type":"library","package_spec":"","url":"/packages/current/security/openssl/3.5/"}],"reverse_dependencies":{"count":0,"url":null},"categories":["net"],"flavors":[],"only_for_architectures":[],"not_for_architectures":[]}}
