0% found this document useful (0 votes)
96 views2 pages

Splunk Interview Prep for Support Engineers

This document serves as a preparation guide for production support interviews, covering key topics such as Grafana alerts, Splunk queries, UNIX commands, SQL questions, Autosys commands, and shell scripting. It includes real-time scenarios, commands, and sample interview questions relevant for candidates with four years of experience. The guide emphasizes troubleshooting techniques and practical examples for effective incident management and monitoring.

Uploaded by

Lokesh Lokesh
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
96 views2 pages

Splunk Interview Prep for Support Engineers

This document serves as a preparation guide for production support interviews, covering key topics such as Grafana alerts, Splunk queries, UNIX commands, SQL questions, Autosys commands, and shell scripting. It includes real-time scenarios, commands, and sample interview questions relevant for candidates with four years of experience. The guide emphasizes troubleshooting techniques and practical examples for effective incident management and monitoring.

Uploaded by

Lokesh Lokesh
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Production Support Interview Prep Sheet (4 Years Experience)

Grafana Real-Time Scenarios & Alerts

1. Memory Usage Alert Not Triggering


- Check PromQL expression and data scrape intervals.
- Use: avg_over_time(memory_usage[5m]) > 85

2. Dashboard shows 'No Data'


- Fix data source (e.g., Prometheus endpoint updated).

3. Alert for CPU usage:


PromQL: 100 - (avg(rate(node_cpu_seconds_total{mode="idle"}[5m])) * 100)
Trigger: > 85% for 5 mins

Splunk Real-Time Scenarios & Queries

1. Missing Logs
- Check forwarder status, [Link] path, restart forwarder.

2. High Error Rate:


Splunk: index=web_logs status=500 | timechart span=5m count

3. Login Failure Alert:


index=auth_logs action="login_failed" | stats count by user | where count > 5

UNIX Common Issues and Commands

1. High CPU Check: top, ps -eo pid,comm,%cpu --sort=-%cpu | head


2. Disk Space Alert Script:
if [ $USAGE -gt 80 ]; then echo "Disk Alert"; fi

3. Troubleshooting:
- Check process: ps -ef | grep app
- Restart with script and validate logs

SQL Interview Questions and Queries

1. Find Duplicates:
SELECT column1, COUNT(*) FROM table GROUP BY column1 HAVING COUNT(*) > 1;

2. Update from Another Table:


UPDATE A SET status='Closed' WHERE EXISTS (SELECT 1 FROM B WHERE [Link] = [Link]);

3. Check Constraint Failures:


Use SELECT to find conflicting records based on error logs.
Production Support Interview Prep Sheet (4 Years Experience)

Autosys Commands and Scenarios

1. Job Status: autostatus -j job_name


2. Force Job: autoforce -j job_name
3. INACTIVE State Fix:
- Check predecessors, dependencies, autoping machine

Shell Scripting Samples

1. File Watch Script:


if [ -f "$FILE" ]; then echo "Exists"; else echo "Missing"; fi

2. Disk Check Script:


USAGE=$(df -h / | awk '{print $5}' | tail -1 | sed 's/%//')
if [ $USAGE -gt 80 ]; then echo "Alert"; fi

3. Service Restart:
- Check health with curl/systemctl
- Restart and notify

Mock Interview Questions

1. What steps do you follow for a P1 incident in Production?


2. How do you monitor and tune alerts in Grafana?
3. Explain a script you wrote to automate a common issue.
4. How do you use Splunk for root cause analysis?
5. Troubleshooting an Autosys job stuck in SU status?

You might also like