Codementor Events

How and Why I Built A Server Monitoring Tool

Published Sep 22, 2017
How and Why I Built A Server Monitoring Tool

About me

I'm an analytical, entrepreneurial, and highly adaptable professional with far-reaching experience in building and managing sophisticated technology services and security solutions for cloud services organizations and financial institutions. I use my extensive leading-edge IT experience to deliver exceptional customer satisfaction and improve overall operations.

The problem I wanted to solve

I needed to have be wherever I needed to be and be able to have my eyes on all the cloud servers that I monitor.

What is a Server Monitoring Tool?

I decided to build a server monitoring tool that runs on both my organization's Linux and Windows servers. This tool monitors the server's hardware resource, logs, and network activities that take place on the server, and alerts me to any new event that hasn't occurred before.

Tech stack

I used Java to build this application because I needed to build this tool on time to run seamlessly across different server operating system platforms. I then used the Netbeans IDE for my development environment.

The process of building a Server Monitoring Tool

I simply looked critically at the problem I needed to solve, identified all possible constraints/requirements, made sure I had all of the necessary resources down, and then began building this tool.

Challenges I faced

I faced challenges with sniffing network traffic on this server, identifying false positive alerts, and more, but I got it all sorted out in the end.

Key learnings

I found better ways to sniff network traffic on operating systems.

Tips and advice

Learn to work smart! Automate tasks when they need to be automated to save time! No one lives forever!

Final thoughts and next steps

Be of value!

Discover and read more posts from Obi Ebuka David
get started
post commentsBe the first to share your opinion
Show more replies