ostent alternatives and similar packages
Based on the "DevOps Tools" category.
Alternatively, view ostent alternatives based on common mentions on social networks and blogs.
-
Moby
The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems -
Gitea
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD -
Packer
Packer is a tool for creating identical machine images for multiple platforms from a single source configuration. -
kubeshark
The API traffic analyzer for Kubernetes providing real-time K8s protocol-level visibility, capturing and monitoring all traffic and payloads going in, out and across containers, pods, nodes and clusters. Inspired by Wireshark, purposely built for Kubernetes -
Ddosify
Anteon (formerly Ddosify) - Effortless Kubernetes Monitoring and Performance Testing. Available on CLI, Self-Hosted, and Cloud -
dasel
Select, put and delete data from JSON, TOML, YAML, XML and CSV files with a single tool. Supports conversion between formats and can be used as a Go package. -
Mizu
DISCONTINUED. The API traffic viewer for Kubernetes providing deep visibility into all API traffic and payloads going in, out and across containers and pods inside a Kubernetes cluster. Think TCPDump and Wireshark re-invented for Kubernetes [Moved to: https://github.com/kubeshark/kubeshark] -
Pomerium
Pomerium is an identity and context-aware reverse proxy for zero-trust access to web applications and services. -
Fleet device management
Open-source platform for IT, security, and infrastructure teams. (Linux, macOS, Chrome, Windows, cloud, data center) -
StatusOK
Monitor your Website and APIs from your Computer. Get Notified through Slack, E-mail when your server is down or response time is more than expected. -
s3gof3r
Fast, concurrent, streaming access to Amazon S3, including gof3r, a CLI. http://godoc.org/github.com/rlmcpherson/s3gof3r -
uTask
µTask is an automation engine that models and executes business processes declared in yaml. ✏️📋
CodeRabbit: AI Code Reviews for Developers
Do you think we are missing an alternative of ostent or a related project?
Popular Comparisons
README
Ostent
Ostent collects metrics to display and report to InfluxDB, Graphite, Librato.
The interactive display UI (demo):
System metrics collected and reported:
- RAM, swap usage
- CPU usage, load average
- Disk space usage in bytes and inodes
- Network ins and outs in bytes, packets, drops and errors
The processes top is on-display only.
Install
Ostent is a single executable. Release tarball has the binary — download and extract in one go:
curl -L https://github.com/ostrost/ostent/releases/download/v0.7.0/`uname`-`uname -m`.tar.xz | tar Jxf -
This will place executable in ./usr/**/bin/ostent
.
For system-wide install use sudo tar Jxf - -C / <<<...
.
Platforms:
- Linux
- FreeBSD
- Mac OS X
Usage
$ ostent -h
Ostent is a server tool to collect, display and report system metrics.
Usage:
ostent [flags]
Flags:
--bind string server bind address (default "")
--bind-port int server bind port (default 8050)
--config string config filename (default "$HOME/.ostent.toml")
--interval duration metrics collection interval (default 10s)
--log-requests log server requests (default false)
--upgrade-checks periodic upgrade checks (default true)
--version print version and exit
Config
Configuration file supports all telegraf settings.
Ostent implementation features extra [agent]
bind
and bind_port
.
Otherwise same structure, sections and options of telegraf config.
Defaults for options and plugins applied when they're not stated in the file.
Each default plugin can be disabled with it's disabled = true
.
Effective runtime config is printed at ostent startup and reload.
To enable reporting to InfluxDB:
[outputs]
[outputs.influxdb]
database = "ostent"
urls = ["http://127.0.0.1:8086"]
Other outputs sections would be [outputs.graphite]
and [outputs.librato]
.
Running the code
go get github.com/ostrost/ostent
ostent
to run.
See also Two kind of builds.
Rebuilding
cd $(go list -f {{.Dir}} github.com/ostrost/ostent)
make init
once.npm install
once, optional, sets up assets and template rebuilding.gulp watch
ormake
after changes.
make
rebuilds these commited to the repo files:
share/assets/bindata.*.go
share/assets/css/*.css
share/assets/js/*/*.js
share/templates/*.html
share/templates/bindata.*.go
share/js/*.jsx
If you don't change source files, content re-generated should not differ from the commited.
gulp watch
- watches share/{js,style,templatesorigin} and rebuilds dependants on changes
- does live-reloading
ostent
code run - acceps all ostent flags e.g.
gulp watch -b 127.0.0.1:8080
Two kinds of builds
Standalone and release binaries produced by make
(or go get -tags bin
)
include embeded template and assets.
Non-bin builds made by gulp watch
and go get
- serve assets and use template from actual files
- have a set of flags facilitating debugging etc.