|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Free and Open Source messaging and emailing app that combines common web applications into one.|
|Alertmanager||6,030||66||359||16 hours ago||156||August 24, 2023||532||apache-2.0||Go|
|Notify||2,514||17||a day ago||64||June 21, 2023||29||mit||Go|
|A dead simple Go library for sending notifications to various messaging services.|
|Noticed||2,082||2||2 days ago||43||May 11, 2023||28||mit||Ruby|
|Notifications for Ruby on Rails applications|
|Handesk||1,288||8 months ago||120||mit||PHP|
|A Powerful Laravel Help Desk and Lead Management App|
|Wavebox, the revolutionary and feature-rich Chromium browser that's built for productive working across Google Workspaces, Microsoft Teams, ClickUp, Monday, Atlassian, Asana, AirTable, Slack, and every other web app you use to get work done.|
|Chronos||738||3 months ago||44||mit||TypeScript|
|📊 📊 📊 Monitors the health and web traffic of servers, microservices, Kubernetes/Kafka clusters, containers, and AWS services with real-time data monitoring and receive automated notifications over Slack or email.|
|Pingme||679||1||10 days ago||23||November 29, 2023||mit||Go|
|PingMe is a CLI which provides the ability to send messages or alerts to multiple messaging platforms & email.|
|Glass Isc Dhcp||510||2 years ago||53||mit||CSS|
|Glass - ISC DHCP Server Interface|
|Workbase Server||286||2 years ago||9||gpl-3.0||Java|
|Slack alternative, email integrated, build with Meteor|
Visit our website at chronoslany.com.
Chronos is a comprehensive developer tool that monitors the health and web traffic for containerized (Docker & Kubernetes) and non-containerized microservices communicated via REST APIs or gRPC, whether hosted locally or on Amazon Web Services (AWS). Use Chronos to see real-time data monitoring and receive automated notifications over Slack or email.
@chronosmicro/trackerNPM package's README, offering comprehensive guidance on utilizing the package to monitor individual applications effectively.
Previously implemented updates:
This is for the latest Chronos version 12.0 release.
In order to use Chronos within your own application, you must have the
@chronosmicro/tracker dependency installed.
@chronosmicro/tracker package tracks your application's calls and scrapes metrics from your system.
npm install @chronosmicro/tracker.
For more details on the NPM package and instructions for how to use it, please view the Chronos NPM Package README.
If you wish to launch the Electron Application in an WSL2 envirronment(Ubuntu) you may need the following commands for an Electron window to appear
Run the following command in the terminal
sudo apt install libgconf-2-4 libatk1.0-0 libatk-bridge2.0-0 libgdk-pixbuf2.0-0 libgtk-3-0 libgbm-dev libnss3-dev libxss-dev
export DISPLAY="`sed -n 's/nameserver //p' /etc/resolv.conf`:0"
NOTE: You must create your own user database
npm run build
npm run dev:appto start the Webpack development server
npm run dev:electronto start the Electron UI in development mode .
npm run build
npm run package
chronos.appexecutable inside the newly created
release-buildsfolder in the root directory.
We provide eight example applications for you to test out both the Chronos NPM package and the Chronos desktop application:
Additional documentation on how Chronos is used in each example can be found in the Chronos NPM Package README.
AWS folder includes 3 example applications with instructions on how to deploy them in AWS platforms. Note that using AWS services may cause charges.
In the folder within the
master branch, we provide a sample dockerized microservices application to test out Chronos and to apply distributed tracing across different containers for your testing convenience.
Refer to the Docker README in the
docker folder for more details.
gRPC folder includes an HTML frontend and an Express server backend, as well as proto files necessary to build package definitions and make gRPC calls. The reverse_proxy folder contains the server that requires in the clients, which contain methods and services defined by proto files.
Refer to the gRPC README in the
gRPC folder for more details.
kubernetes folder includes a React frontend and an Express server backend, and the Dockerfiles needed to containerize them for Kubernetes deployment. The launch folder includes the YAML files needed to configure the deployments, services, and configurations of the frontend, backend, Prometheus server, and Grafana.
Refer to the Kubernetes README in the
kubernetes folder for more details.
microservices folder, we provide a sample microservice application that successfully utilizes Chronos to apply all the powerful, built-in features of our monitoring tool. You can then visualize the data with the app.
Refer to the microservices README in the
microservices folder for more details.
We've created testing suites for Chronos with React Testing, Jest, and Selenium for unit, integration, and end-to-end tests - instructions on running them can be found in the testing README.
Development of Chronos is open source on GitHub through the tech accelerator OS Labs, and we are grateful to the community for contributing bug fixes and improvements.
Read our contributing README to learn how you can take part in improving Chronos.