Sanjay Kumar Garlapenta

Sanjay writes Merik's guides on monitoring and reliability, task tracking, client work and the sensible use of AI in small teams.

Every guide shows the date it was published and, where it has changed, the date it was last updated. Questions or corrections: merik.msk@gmail.com. Merik on LinkedIn.

Guides by Sanjay Kumar Garlapenta (50)

• 10 production issues your monitoring should detect automatically
• Agency utilisation rate: calculate it, read it, raise it
• AI agents in HR and payroll: what to let them do
• AI in HR software: what helps, what's theatre
• Alert fatigue in small teams: why you ignore your own monitoring
• Application health monitoring: the complete guide
• Application monitoring for startups: what to monitor first
• Backend errors that break your product without crashing it
• Catching scope creep early in the task log
• Choosing HR software: a buyer's checklist
• Daily task tracking that builds accountability
• Did the deploy break production? Correlating deployments with incidents
• Do you need a public status page? A guide for small teams
• Error budgets and SLOs for small teams: a practical introduction
• Finding the software seats nobody uses
• From quote to invoice, without retyping
• From spreadsheets to one workspace, in 30 days
• Frontend errors: why users see problems before your team does
• How AI helps detect application problems before they become incidents
• How proactive monitoring stops small bugs becoming major incidents
• How to detect API failures before your customers do
• How to detect broken user flows before customers complain
• How to monitor JavaScript console errors in production
• How to reduce MTTD — mean time to detect — for application issues
• How to run daily standups without a meeting
• Is it us or them? Handling third-party outages in a small team
• Measuring productivity without micromanaging
• Pricing a retainer from your own data
• Project profitability, from hours you already log
• Reactive vs proactive monitoring: what’s the difference?
• SSL certificate expiry monitoring: why shorter certificates make it mandatory
• Structure clients and projects so reporting works
• Synthetic monitoring vs real user monitoring: what each sees
• The asset register you actually need
• The complete guide to proactive application reliability
• The hidden cost of silent application failures
• The monthly SLA report: what to include, how to compute it
• The MSME 45-day payment rule: how an agency gets paid on time
• Timesheets vs daily task logs: which one does your team need?
• Uptime monitoring tools for small teams: what to compare, and a shortlist
• Website monitoring for agencies: every client site, no ops person
• What is observability — and how is it different from monitoring?
• What is proactive application monitoring?
• What should you monitor in a SaaS application?
• Why logs alone are not enough for modern application monitoring
• Why waiting for users to report bugs is too late
• Why your time estimates are always wrong
• You built it with AI. Now it is in production. Here is what breaks
• Your application is up. So why are users still having problems?
• Your product depends on an LLM API. Monitor it before users notice

Also from Merik: guides by Mounika Garlapenta, Founder & CEO. More about the company on the About page.