Skip to content

Latest commit

 

History

History
168 lines (66 loc) · 5.99 KB

File metadata and controls

168 lines (66 loc) · 5.99 KB

INTRODUCTION

Stork is a set of command line helpers for Databricks. Some commands are for managing libraries in Databricks in an automated fashion. This allows you to move away from the point-and-click interface for your development work and for deploying production-level libraries for use in scheduled Databricks jobs. Another command allows you to create an interactive cluster that replicates the settings used on a job cluster.

PROJECT SUMMARY

Website hi@portworx.com
Organization/ Foundation Name # Portworx
License BSD 2-Clause License
-Open/Proprietary- -Open Source-
Source Code Source Code
Brief description Stork is an open source monitoring application and dashboard for ISC’s Kea DHCP, and eventually for ISC’s BIND 9. It is the spiritual successor of the earlier projects Kittiwake and Anterius.

Website

hi@portworx.com

Organization/ Foundation Name

Portworx

License

BSD 2-Clause License

Open/Proprietary

Open Source

Source Code

https://github.com/ShopRunner/stork.git

Brief description

Stork is an open source monitoring application and dashboard for ISC’s Kea DHCP, and eventually for ISC’s BIND 9. It is the spiritual successor of the earlier projects Kittiwake and Anterius.

PROJECT DETAILS

Key Features

  • Local authentication with admin and super-admin privilege levels

  • Stork agent deployed on the Kea or BIND server reports CPU and OS data, including speed, memory, memory utilization, operating system and version.

  • Auto-discovery of Kea and BIND services on monitored machines with application software version and uptime since last reload

  • Prometheus and Grafana integration

  • DHCP pool utilization

  • DHCP Shared network utilization

  • DHCP High Availability status monitoring

  • DHCP Host reservations

  • BIND9 Cache Hit Ratio monitoring

Architecture

The Stork server is installed on a stand-alone machine. It connects to any indicated agents and indirectly (via those agents) interacts with the Kea DHCP services. It provides an integrated, centralized front end for these services. Only one Stork server is deployed in a network.

The Stork agent is installed along with Kea DHCP and interacts directly with those services. There may be many agents deployed in a network, one per machine.

Current Usage

Amazon Web Services

AWS

Cloud Computing

CloudFlare

Cloudflare

DNS & SSL

Sentry

Sentry

Monitoring

Elastic

Elastic

Search

New Relic

New Relic

Performance

PagerDuty

PagerDuty

Monitoring

Other Information

There are public mailing lists available for the Stork project. stork-users (stork-users at lists.isc.org) is intended for Stork users. stork-dev (stork-dev at lists.isc.org) is intended for Stork developers, prospective contributors, and other advanced users. The lists are available at https://www.isc.org/mailinglists/. The community provides best-effort support on both of those lists.