Rootconf 2018

With increasing servers, applications, crons (schedule jobs) it was becoming pain to manage and monitor all crons.
We thus built NCConfig – a tool to monitor all crons which includes their status – Success/Failure, executing time, output, etc

Few major problems which we used to face before building NCConfig

– Did my job actually run?
Generally all crons were used to be monitored via email now because the typical way to monitor cron jobs is via email it is often extremely hard to find out if a job has actually run successfully. Ideally your monitoring shouldn’t involve people being awake and willing to read automatically generated emails. Especially if the cron job is important.

– Email, email everywhere!
Cron used to email the output of a given job to the user that the job is running as. This can be very useful when some aspect of the job requires alerting the user.
The problem is that you very often do not want emails from cron jobs. And usually when they start they can flood your inbox very fast.

– Where is my cron running ?
With more than 100 serves and single applications running on multiple servers its sometime get difficault to find where actually is my cron running.

– Execution Statistics
You may see the cron job execution statistics (including the total number of successful executions, total number of failed executions (TF) and number of consecutive failed executions (CF)) in the cron job list

Feature details :

• Centralized system to manage all your crons running on multiple servers.
• Execution Statistics – You can get the time taken for each and every cron using this tool (Start Time, End Time)
• Graphical Statistics – You can check the execution statistics in graphical format
• Role based Management – Admin / Application Manager / Read Only
  – Admin : Will have all the rights like adding server, application, crons. etc
  – Application Manager – Will have the rights to manage the crons of the application which they own.
  – Ready Only – Will have only read only access
• Cron Success/Failure logs – Stores all the output of the crons in the databases which can be accessed anytime and also the cron status
• Single Change Settings – includes any actions that can change cron job settings excepting “Enable Logs”, “Disable Logs”, “Enable Cron Job” and “Disable Cron Job”.
• Easy Integration – One-time setup/integration with your existing environment.
• NCConfig is totally free for non-commercial use.
• You can modify the source code to suit your system and use it internally, as well as develop customized tools aggregating features to NCConfig.
• All settings and the values collected are stored in a simple format and are fully open

You can download the NCConfig from here https://github.com/naukri-engineering/NCConfig

Outline

What I’II Talk About
○ Major problems which we used to face before building NCCron
○ Features of NCCron
○ Walk-through of NCCron

Speaker bio

About Me :

• Working with Info Edge India Ltd (Naukri.com) as Vice President - Engineering
• Over 12 years of experience in Internet Technology having expertise in managing & scaling high traffic websites
• Deliver high-quality software/projects through a mix of software engineering, management and technical expertise.
• Over 7 years of experience in managing teams including Technical Architects & Engineering Managers; developing complex products for large enterprises and masses.
• Responsible for all aspects of Software Development, including resource allocation, project management and delivery.
• Expertise in working with high-traffic application, profiling and improving performance and scalability.

Slides

https://docs.google.com/presentation/d/18N8SbY982Sl5oRAI4U0gCGG72TU84dizmw9T4SGuW7Y/edit?usp=sharing