Kubernetes Pod Logs Monitoring & AI Analysis | Nife Deploy
View real-time logs from your pods and use AI-powered analysis to understand issues.
Pod Logs Overview#
Pod logs show output from your running applications in the cluster.
What are Pod Logs?#
Pod logs are text output generated by applications:
- Application startup messages
- Errors and warnings
- Debug information
- Info messages
- Business events
Why View Logs?#
- Troubleshooting: Find out what went wrong
- Debugging: Understand application behavior
- Monitoring: Watch real-time activity
- Auditing: Record what happened
- Analysis: Find patterns and issues
Accessing Pod Logs#
Option 1: Via Dashboard#
- Go to Clusters page
- Select cluster with agent
- Click Pod Logs tab
- Select application from dropdown
- Click Fetch Logs or Stream Logs
Option 2: Via Command Line#
Fetching Logs#
One-Time Fetch#
Get a snapshot of recent logs:
Select Application
- Choose app from dropdown
- Select how many lines:
- 50 lines: Last few seconds
- 100 lines: Last minute
- 500 lines: Last 5 minutes
- 1000 lines: Last 10 minutes
Click Fetch Logs
- Wait for logs to load
- Results appear in viewer
View Results
- See log entries with timestamps
- Each line shows log level and message
Log Format#
Streaming Logs#
Watch logs in real-time as they're generated:
Start Streaming#
Select Application
- Choose the app to monitor
- Only one stream at a time
Click Stream Logs
- Live logs start appearing
- New entries appear at bottom
- Stream indicator shows status
Streaming Features#
Auto-Scroll:
- Toggle "Auto-scroll" on/off
- When on: Jumps to newest entry
- When off: Stay at current position
Search:
- Type in search box
- Filters logs in real-time
- Shows matching entries
- Case-insensitive
Filter by Level:
- All Levels: Show everything
- Error: Only error messages
- Warn: Warnings and errors
- Info: Info and above
- Debug: All messages
Stop Streaming#
- Click Stop Stream button
- Live updates stop
- View your captured logs
- Can export or analyze
Filtering and Searching#
Search Logs#
Find specific messages:
Enter search term
- Type what you're looking for
- Search is real-time
Results update
- Only matching logs shown
- Count shows matches found
Clear search
- Delete search text
- All logs appear again
Filter by Level#
Show only certain severity:
Example Searches#
Find database errors:
Find timeout errors:
Find a user's activity:
Exporting Logs#
Save logs for analysis or archival:
Export Options#
Export as Text (.txt)
- Plain text format
- Easy to read
- Good for sharing
- Use for: Documentation, emails
Export as JSON (.json)
- Structured format
- Includes metadata
- Machine-readable
- Use for: Analysis tools, automation
How to Export#
Load or filter logs
- Fetch or stream logs first
- Filter to what you want
Click Export
- Choose format (TXT or JSON)
- File downloads automatically
Use exported logs
- Analyze offline
- Share with team
- Import to analysis tools
- Archive for compliance
AI-Powered Log Analysis#
Use AI to automatically analyze logs and find issues.
What AI Analysis Does#
The AI analyzes your logs to:
- Detect Issues: Find errors and problems
- Identify Patterns: Spot recurring issues
- Provide Recommendations: Suggest fixes
- Explain Problems: Describe what went wrong
Using AI Analysis#
Step 1: Prepare Logs#
Option A: Use Current Pod Logs
- Toggle "Use current pod logs" ON
- Make sure logs are loaded
- Shows how many entries will be analyzed
Option B: Paste Logs Manually
- Toggle "Use current pod logs" OFF
- Paste your logs in the text area
- Any log format is fine
Step 2: Run Analysis#
- Click Analyze with AI
- Wait for analysis (usually 10-30 seconds)
- Hourglass icon shows progress
- Results appear when ready
Step 3: Review Results#
AI provides:
- Summary: What happened overall
- Issues Found: Specific problems detected
- Severity: How serious each issue is
- Recommendations: How to fix
Understanding AI Analysis Results#
Analysis Summary#
Brief overview of what AI found:
Issues Detected#
Specific problems found:
| Issue | Severity | Description |
|---|---|---|
| Database Connection Timeout | High | Could not connect to database |
| Memory Leak | Medium | Memory usage growing over time |
| Slow Query | High | Query taking 5+ seconds |
Recommendations#
How to fix each issue:
Patterns Found#
Recurring issues and trends:
Interpreting AI Insights#
Issue Severity Levels#
Critical: 🔴
- Application is down or failing
- Immediate action required
- Fix immediately
High: 🟠
- Performance degraded
- Users affected
- Fix very soon
Medium: 🟡
- Minor issues
- Should be addressed
- Fix when convenient
Low: 🔵
- Informational
- Good to know
- Can defer
Common Troubleshooting Scenarios#
Scenario 1: Application Keeps Crashing#
Logs show:
AI Analysis suggests:
- Insufficient memory allocated
- Possible memory leak
- Large data processing causing spike
Solutions:
- Increase pod memory limit
- Check for memory leaks in code
- Process data in smaller chunks
- Enable memory profiling
Scenario 2: Database Errors#
Logs show:
AI Analysis suggests:
- Database server unreachable
- Network connectivity issues
- Connection pool exhausted
Solutions:
- Verify database is running
- Check firewall rules
- Increase connection pool
- Review network configuration
Scenario 3: High Latency#
Logs show:
AI Analysis suggests:
- Slow queries
- External API delays
- Resource contention
Solutions:
- Optimize database queries
- Add caching
- Use CDN for external assets
- Scale cluster resources
Best Practices#
1. Regular Monitoring#
- Check logs daily
- Monitor trends
- Act on warnings
- Review errors
2. Use Streaming for Live Issues#
- Stream when troubleshooting
- Watch real-time behavior
- Easier than fetching later
- See issue as it happens
3. Use AI Analysis Regularly#
- Run weekly analysis
- Track recurring issues
- Monitor for patterns
- Proactive problem finding
4. Export and Archive#
- Export important logs
- Keep for compliance
- Analyze historical patterns
- Document issues
5. Set Up Alerts#
- Alert on error rates
- Alert on specific errors
- Alert on performance degradation
- Set up escalation
Log Retention#
How Long are Logs Kept?#
- Real-time logs: 7 days
- Archived logs: 30 days
- Compliance logs: 1 year (if enabled)
Exporting Before Expiration#
If you need logs longer:
- Export before expiration date
- Store in your own system
- Archive as needed
- Use for analysis later
Limitations#
Maximum Log Entries#
- Fetch: Up to 1000 lines
- Stream: Keeps last 500 lines
- Export: Based on what's loaded
Network Requirements#
- Stable internet connection
- 1+ Mbps bandwidth for streaming
- Some browsers better than others
App Requirements#
- Application must have agent deployed
- Agent must have Logging capability
- Application must output logs to stdout/stderr
Next Steps#
- View Security Findings - Check cluster security
- Manage Resources - Monitor cluster health
- Deploy Applications - Use your cluster
Support#
Questions about logs?
- Check the scenarios above
- Review AI analysis suggestions
- Contact support: [email protected]
Logs not appearing?
- Verify agent is deployed
- Check agent status
- Ensure Logging capability enabled
- Verify application outputs logs