You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-18Lines changed: 25 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -23,38 +23,44 @@ Chronos is a comprehensive developer tool that monitors the health and web traff
23
23
24
24
## What's New?
25
25
26
+
- Chronos is now able to work out of the box, addressing previous bugs that prevented Chronos to work as intended. File structure, dependencies, and webpack entry point have been updated, allowing Chronos Electron desktop application to run on multiple platforms.
27
+
- User's account information and services can now be stored and saved in MongoDB User database.
28
+
- Bug fixes and UI tweaks — Chronos is now a faster and more seamless experience than ever.
29
+
- Updated step-by-step instructions to learn how to deploy local services such as dockerized containers, microservices, and gRPC examples, as well as monitor them using the chronosmicro/tracker npm package.
30
+
- Steamlined approach to access and dynamically displayed grafana dashboards for deployed EKS cluster (utilizing Prometheus data scraping and generated grafana dashboards) using the Grafana API.
31
+
32
+
Previously implemented updates:
26
33
- Option to choose between cloud hosted services and local services, now giving Chronos the ability to monitor instances and clusters on AWS' EC2, ECS, and EKS platforms.
27
34
- An updated AWS Graphs Container to dynamically render plots for EC2 or ECS data fetched with Electron using event listeners connecting to AWS CloudWatch w/ the aws-sdk package, as well as utilizing Prometheus data scraping and Grafana integration to fetch and render EKS data.
28
35
- A step-by-step instruction on setting up a new, functional EC2 instance, ECS cluster, and EKS cluster, ready to be monitored and tested by the app.
29
-
- Bug fixes and UI tweaks — Chronos is now a more seamless experience than ever.
30
36
31
37
## Features
32
38
33
-
- Distributed tracing enabled across microservices applications
34
-
- Kubernetes monitoring via Prometheus server
35
-
- Compatible with <imgsrc="assets/graphql-logo-color.png"alt="GraphQL"title="GraphQL"align="center"height="20" /></a>
36
-
- Supports <ahref="#"><imgsrc="assets/postgres-logo-color.png"alt="PostgreSQL"title="PostgreSQL"align="center"height="20" /></a> and <imgsrc="assets/mongo-logo-color.png"alt="MongoDB"title="MongoDB"align="center"height="20" /></a> databases
37
-
- Displays real-time temperature, speed, latency, and memory statistics
38
-
- Display and compare multiple microservice metrics in a single graph
39
-
- Monitor an <ahref="#"><imgsrc="assets/pngwing.com.png"alt="Apache Kafka"title="Apache Kafka"align="center"height="20" /></a> cluster via the JMX Prometheus Exporter
40
-
- Monitor a Kubernetes cluster via a Prometheus monitoring server
41
-
- Monitor Amazon Web Services (AWS) instances and clusters <imgsrc="assets/aws-logo-color.png"alt="AWS"title="AWS"align="center"height="20" /></a>
39
+
- Cloud-Based Instances:
40
+
- Option to choose between cloud hosted services and local services, now giving Chronos the ability to monitor instances and clusters on AWS' EC2, ECS, and EKS platforms <imgsrc="assets/aws-logo-color.png"alt="AWS"title="AWS"align="center"height="20" /></a>
41
+
- Local Instances utilitizing @chronosmicro/tracker NPM package:
42
+
- Distributed tracing enabled across microservices applications
43
+
- Displays real-time temperature, speed, latency, and memory statistics for local services
44
+
- Display and compare multiple microservice metrics in a single graph
45
+
- Kubernetes monitoring via Prometheus server
46
+
- Compatible with <imgsrc="assets/graphql-logo-color.png"alt="GraphQL"title="GraphQL"align="center"height="20" /></a>
47
+
- Monitor an <ahref="#"><imgsrc="assets/pngwing.com.png"alt="Apache Kafka"title="Apache Kafka"align="center"height="20" /></a> cluster via the JMX Prometheus Exporter
48
+
- Supports <ahref="#"><imgsrc="assets/postgres-logo-color.png"alt="PostgreSQL"title="PostgreSQL"align="center"height="20" /></a> and <imgsrc="assets/mongo-logo-color.png"alt="MongoDB"title="MongoDB"align="center"height="20" /></a> databases
42
49
43
50
#
44
51
45
52
## Installation
46
53
47
-
This is for the latest Chronos **version 9 release**.
54
+
This is for the latest Chronos **version 10 release**.
48
55
49
56
**NOTE:** The Chronos tracker code is included in the _chronos_npm_package_ folder for ease of development, but the published npm package can be downloaded by running `npm install @chronosmicro/tracker`
50
57
51
58
<br>
52
59
53
-
### Node Version
54
-
55
-
Make sure you're running version 16.17.1 of <imgsrc="assets/node-logo-color.png"alt="Node"title="Node"align="center"height="20" />, to align with the <imgsrc="assets/node-logo-color.png"alt="Node"title="Node"align="center"height="20" /> version used by <imgsrc="assets/electron-logo-color.png"alt="Electron"title="Electron"align="center"height="20" /> version 22.
56
-
57
-
<br>
60
+
<!-- ### Node Version -->
61
+
<!-- v10 notes: Our team never reverted to version 16.17.1 and had no issues running Node 18 and Electron 22 together. Commenting this out for future iteration teams' reference. -->
62
+
<!-- Make sure you're running version 16.17.1 of <img src="assets/node-logo-color.png" alt="Node" title="Node" align="center" height="20" />, to align with the <img src="assets/node-logo-color.png" alt="Node" title="Node" align="center" height="20" /> version used by <img src="assets/electron-logo-color.png" alt="Electron" title="Electron" align="center" height="20" /> version 22. -->
0 commit comments