one-zero-eight / one-zero-eight/server
Scripts that check innohassle.ru availability from different nets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the feature
We want to track when InNoHassle was inaccessible because of network problem and get the statistics of downtimes.
Suggested solution
Create a script that constantly makes requests to innohassle.ru and api.innohassle.ru. If there is a problem, it should notify us via Telegram in the start and in the end of the issue.
The script should be run on different servers: inside Innopolis (also in different subnets), in Russia, and outside of Russia, so we can understand where the issue exists.
Additional context
You could also check the time of request:
curl -w "\nDNS: %{time_namelookup}s\nConnect: %{time_connect}s\nTTFB: %{time_starttransfer}s\nTotal: %{time_total}s\n" -o /dev/null -s https://innohassle.ru
DNS: 0.086959s
Connect: 0.090406s
TTFB: 0.166713s
Total: 0.166766s
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the repository's Python and VM configuration structure, then define how checks will run from each network and how downtime statistics will be stored. Done means availability checks cover both listed endpoints, notify Telegram at outage start and end, and record request timing and network location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, networking, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100