Role Monitoring and Automation Engineer (L2): addendum to the

core CIMS Platform Engineer JD

Seats (Year 1 / Year 3) 2 / 1

Location India-based. 24x7 shifts with handover overlap. On-call rota for

escalation.

Minimum experience 4+ years running Nagios or LogicMonitor at enterprise scale,

with hands-on configuration (proposed, pending approval).

Reports to Technical Lead (L2 lead for monitoring)

Purpose

The monitoring and automation engineer is the first defence against noise. Most of the client's incidents are raised by

automated alert feeds, and most of the low-priority volume is alert noise. This role owns the CIMS monitor content in

Nagios and LogicMonitor, tunes thresholds and dependencies to cut false alarms, keeps the monitor register and coverage

inventory current, and automates safe responses such as auto-explicit rules. Nagios and LogicMonitor are the client's

platforms; this role adds and maintains the CIMS checks.

Responsibilities

 Maintain CIMS Nagios configuration as part of each application deployment: queue count and age, listener liveness,

application liveness, exceptions, 997 reconciliation, Old File, SAP ALE acknowledgement, messaging health checks and

volume trend. Also the custom CIMS application monitors, learned during knowledge transfer.

 Tune alerts to cut false alarms: retry and check attempts, flap detection, host and service dependencies, scheduled

downtime and event handlers.

 Run the monthly alert review: find the top noise patterns, propose rule changes under change control and report the

false-alarm share.

 Keep the monitor coverage register current: map each critical service and interface to its monitors; test monitors on

introduction and after change.

 Add or adjust monitoring after each P1 or P2 that monitoring did not detect first.





 Write scripts for checks that the platform tools do not provide, under version control and with exit codes Nagios can

read.

Must-have skills

 Nagios configuration in production: objects, commands, check plugins, retries, flap detection, dependencies and

event handlers (must-have).

 LogicMonitor or an equivalent monitoring platform: data sources, alert rules and thresholds (must-have).

 Alert tuning with evidence: reduces false alarms without losing real detections (must-have).

 Pattern-based log alerting: regular-expression include and exclude rules, tuned to avoid noise (must-have).

 Scripting (Bash plus Python or Perl) for monitoring checks, with exit codes and logging (must-have).

 ServiceNow integration: alerts creating incidents once, with the right priority and routing (must-have).

Job description. Anonymised for posting. Confirm before publishing.

 Linux command line and metrics: CPU, memory, swap, disk and inode, process health (must-have).

 AI-assisted delivery: uses an approved AI assistant to review alert trends and draft check code, and checks the output

(must-have).

Nice to have

 Dynatrace or another application performance tool, where McKesson has approved it.

 JBoss or JVM metrics (heap, threads, pool use).

 Git-based configuration management for monitoring content.

Tools

Nagios (CIMS instance); LogicMonitor; ServiceNow; Git; Bash; Python; GitHub Copilot.

How success is measured

 False-alarm share of alert-raised P2s, reported monthly, falling from the baseline.

 Share of low-priority noise closed by the system, rising from the baseline, with each auto-clear rule approved.

 Monitors tested with evidence; no P1 or P2 that monitoring should have caught.

Pay: ₹324,000.00 - ₹1,420,000.00 per year

Work Location: Remote

📌 Monitoring and Automation Engineer (India)
🏢 Ultrafly Solutions Private
📍 India