Harkishen Singh

Results 50 issues of Harkishen Singh

Right now bench-routes monitors GET and POST request only. This should be extended for all HTTP supported request to types.

enhancement
priority:high

Currently, system-metrics monitor the following: 1. CPU usage (percent) 2. Memory usage (percent) 3. Memory cache 4. Disk I/O There are tons of other details that are required: 1. Network...

feature
priority:high
server-side
golang

**Is your feature request related to a problem? Please describe.** Currently, the user has no idea if the configuration file made by him is valid or not, depending on the...

priority
feature
server-side
golang

The `sleep` in main go-routine handling ping makes the entire thread sleep only when all the ping operation on the routes mentioned in the config file has been done _(a...

enhancement
priority

Follow on #42. Proposal for alerting method via mails. This will involve the necessary changes in the configuration file, as the required credentials needed for setting up a mailing system...

feature

Bench-routes provides support for multiple platforms. Features like monitoring can be performed on all platforms. However, those functionalities which require the help of subprocess (say `ping`, `flood ping`) are dependent...

enhancement
good to have
dashboard

OS: universal #### Describe Network Congestion is the situation which occurs when the entire bandwidth of the network is occupied. Any request in a congested network will be bound to...

feature
bench-routes-init
priority:high

Right now, the querier queries only the time-series files. This means that querying is possible only on the data that has been flushed and not the one in-memory. This creates...

enhancement
priority:high

TSDB is saved in `.json`. This is space-intensive. We need to implement this on the legacy tsdb blocks and compress using high compression algorithms like 7zip (preferred), zw, bzip2.

feature

We do querying in order to form and visualize graphical values. This involves time. Capture this time and pass it via existing functionality.

duplicate
good first issue
feature