Blog-Api-Server on Yarang's Tech Lair

[blog-api-server] MCP Blog Client Language Parameter

Tue, 03 Mar 2026 23:19:28 +0900

[blog-api-server] MCP Blog Client Language Parameter

Overview

Added a language parameter to the MCP (Model Context Protocol) blog client for improved Korean/English multilingual blog management.

Changes

blog_create Tool Update

Tool(
 name="blog_create",
 description="Create a blog post. Provide title and content (Markdown), and the post will be created and committed/pushed to Git.",
 inputSchema={
 "type": "object",
 "properties": {
 "title": {"type": "string", "description": "Post title"},
 "content": {"type": "string", "description": "Post content (Markdown)"},
 "tags": {"type": "array", "items": {"type": "string"}, "description": "Tag list"},
 "categories": {"type": "array", "items": {"type": "string"}, "description": "Category list"},
 "draft": {"type": "boolean", "description": "Draft status (default: false)"},
 "language": {"type": "string", "description": "Language (ko, en). Default: ko"} # New
 },
 "required": ["title", "content"]
 }
)

API Call Logic

if name == "blog_create":
 result = await client.request("POST", "/posts", data={
 "title": arguments["title"],
 "content": arguments["content"],
 "tags": arguments.get("tags", []),
 "categories": arguments.get("categories", ["Development"]),
 "draft": arguments.get("draft", False),
 "language": arguments.get("language", "ko"), # Default: Korean
 "auto_push": True
 })

Usage

Using in Claude Code

{
 "mcpServers": {
 "blog": {
 "command": "python3",
 "args": ["/path/to/mcp_blog_client.py"],
 "env": {
 "BLOG_API_URL": "https://blog.fcoinfup.com",
 "BLOG_API_KEY": "your_api_key"
 }
 }
 }
}

Creating Korean Posts

{
 "tool": "blog_create",
 "arguments": {
 "title": "[프로젝트명] 포스트 제목",
 "content": "# 내용\n\n마크다운 형식의 내용...",
 "tags": ["tag1", "tag2"],
 "categories": ["Development"],
 "language": "ko"
 }
}

Creating English Posts

{
 "tool": "blog_create",
 "arguments": {
 "title": "[Project Name] Post Title",
 "content": "# Content\n\nMarkdown formatted content...",
 "tags": ["tag1", "tag2"],
 "categories": ["Development"],
 "language": "en"
 }
}

API Examples

Request Format

curl -X POST https://blog.fcoinfup.com/api/posts \
 -H "X-API-Key: your_api_key" \
 -H "Content-Type: application/json" \
 -d '{
 "title": "[blog-api-server] Test Post",
 "content": "# Test\n\nThis is a test post.",
 "tags": ["test"],
 "categories": ["Development"],
 "language": "en",
 "auto_push": true
 }'

Response Format

{
 "success": true,
 "filename": "2026-03-03-001-blog-api-server-test-post.md",
 "path": "/content/en/post/2026-03-03-001-blog-api-server-test-post.md",
 "git": {
 "success": true,
 "commit": "abc123...",
 "branch": "main"
 }
}

File Path Rules

Language	language Value	Storage Path
Korean	`ko`	`content/ko/post/`
English	`en`	`content/en/post/`

Future Plans

Translation Automation: Auto-translation feature using language parameter
i18n Links: Automatic link generation between KO/EN posts
Extended Language Support: Japanese, Chinese, and more

Conclusion

The language parameter addition to the MCP blog client enables more convenient multilingual blog management directly from Claude Code.

Korean Version: 한국어 버전

[blog-api-server] Monitoring Dashboard and Alerting System

Tue, 03 Mar 2026 14:53:47 +0900

[blog-api-server] Monitoring Dashboard and Alerting System

Overview

A Prometheus-based monitoring system and Slack/Email alerting have been added to blog-api-server, enabling real-time server status tracking and immediate response to issues.

Monitoring Architecture

flowchart TB
 A[HTTP Request] --> B[MonitoringMiddleware]
 B --> C[Request Logging]
 B --> D[PrometheusMiddleware]
 D --> E[Metrics Collection]
 C --> F[AlertManager]
 E --> F
 F --> G{Threshold Check}
 G -->|Over Threshold| H[Slack Webhook]
 G -->|Critical| I[Email Alert]
 G -->|Normal| J[Log Only]
 K[Prometheus Server] --> L[/metrics/prometheus]
 M[Dashboard] --> N[/dashboard]

Prometheus Metrics

Basic HTTP Metrics

Metric	Type	Labels	Description
`http_requests_total`	Counter	method, endpoint, status	Total HTTP requests
`http_request_duration_seconds`	Histogram	method, endpoint	Request latency distribution
`http_errors_total`	Counter	method, endpoint, status	Total error count
`active_requests`	Gauge	-	Current active requests

Business Metrics

Metric	Type	Labels	Description
`git_operations_total`	Counter	operation, status	Git operation count
`git_operation_duration_seconds`	Histogram	operation	Git operation duration
`translation_requests_total`	Counter	source_lang, target_lang, status	Translation request count
`translation_duration_seconds`	Histogram	-	Translation duration
`post_operations_total`	Counter	operation, language, status	Post operation count

Metrics Collection Code

# prometheus_exporter.py
from prometheus_client import Counter, Histogram, Gauge

http_requests_total = Counter(
 'http_requests_total',
 'Total HTTP requests',
 ['method', 'endpoint', 'status']
)

http_request_duration_seconds = Histogram(
 'http_request_duration_seconds',
 'HTTP request latency',
 ['method', 'endpoint']
)

# Auto-collection in middleware
class PrometheusMiddleware(BaseHTTPMiddleware):
 async def dispatch(self, request: Request, call_next):
 start_time = time.time()
 response = await call_next(request)
 duration = time.time() - start_time

 http_requests_total.labels(
 method=request.method,
 endpoint=request.url.path,
 status=response.status_code
 ).inc()

 http_request_duration_seconds.labels(
 method=request.method,
 endpoint=request.url.path
 ).observe(duration)

Alerting System

Alert Rules

Rule Name	Condition	Severity	Cooldown
High Error Rate	error_rate > 5%	WARNING	5 min
Critical Error Rate	error_rate > 20%	CRITICAL	1 min
Slow Response Time	avg_response_time > 2000ms	WARNING	10 min
High Slow Request Rate	slow_request_rate > 10%	WARNING	5 min

Alert Channels

Slack Webhook

Supports all severity levels
Color-coded severity (INFO: green, WARNING: orange, ERROR: red, CRITICAL: dark red)

Email

CRITICAL level only
SMTP-based email delivery

AlertManager Code

# alerting.py
class AlertManager:
 def check_and_alert(self, metrics: Dict[str, Any]):
 for rule in self.rules:
 if rule.should_trigger(metrics):
 self._send_alert(rule, metrics)

 def _send_alert(self, rule: AlertRule, metrics: Dict[str, Any]):
 message = f"""
Alert Rule: {rule.name}
Condition: {rule.condition}

Current Metrics:
- Total Requests: {metrics.get('total_requests', 0)}
- Error Count: {metrics.get('error_count', 0)}
- Error Rate: {metrics.get('error_rate_percent', 0)}%
- Slow Requests: {metrics.get('slow_request_count', 0)}
"""
 self.slack.send(
 title=f"Alert: {rule.name}",
 message=message.strip(),
 severity=rule.severity
 )

Dashboard Configuration

Monitoring Endpoints

Path	Auth	Description
`/health`	Not Required	Server health check
`/metrics`	Required	JSON format metrics
`/metrics/prometheus`	Not Required	Prometheus format metrics
`/metrics/reset`	Required	Reset metrics
`/dashboard`	Not Required	Web dashboard
`/alerts/rules`	Required	Alert rules list
`/alerts/send`	Required	Manual alert send

Request Tracking Middleware

# middleware.py
class MonitoringMiddleware(BaseHTTPMiddleware):
 async def dispatch(self, request: Request, call_next):
 request_id = str(uuid.uuid4())
 start_time = time.time()

 response = await call_next(request)
 process_time = (time.time() - start_time) * 1000

 # Add tracking info to response headers
 response.headers["X-Process-Time"] = f"{process_time:.2f}"
 response.headers["X-Request-ID"] = request_id

 return response

Environment Variables

# Slack Alerts
SLACK_WEBHOOK_URL=https://hooks.slack.com/services/...

# Email Alerts
SMTP_SERVER=smtp.gmail.com
SMTP_PORT=587
SMTP_USERNAME=your-email@gmail.com
SMTP_PASSWORD=your-app-password
ALERT_FROM_EMAIL=your-email@gmail.com
ALERT_TO_EMAILS=admin@example.com,ops@example.com

# Threshold Settings
SLOW_REQUEST_THRESHOLD=1000 # 1 second
VERY_SLOW_THRESHOLD=3000 # 3 seconds
MAX_BODY_LOG_LENGTH=1000

Future Plans

Grafana Integration: Visualize Prometheus data in Grafana dashboard
Dynamic Alert Rules: API to add/remove alert rules at runtime
Metrics Retention: Long-term metrics storage and analysis
Enhanced Health Checks: Dependency service (Git, LLM) status checks

Conclusion

With Prometheus-based monitoring and Slack/Email alerting, infrastructure is now in place for real-time server monitoring and immediate incident response.

Korean Version: 한국어 버전

[blog-api-server] LLM Config Improvement and Deployment

Tue, 03 Mar 2026 13:01:48 +0900

Overview

Improved the LLM configuration for the blog-api-server project and deployed it to the server.

LLM Configuration Improvements

Existing Issues

Multiple API key environment variables (ZAI_API_KEY, ANTHROPIC_API_KEY)
Complex provider branching logic
Scattered model settings

Changes

Environment Variable Simplification

# Before
ZAI_API_KEY=xxx
ANTHROPIC_API_KEY=xxx
ZAI_MODEL=gpt-4o-mini
LLM=ZAI

# After
LLM=ZAI # Provider (ZAI, OPENAI, ANTHROPIC)
LLM_API_KEY=xxx # Single API Key
LLM_MODEL=glm-4.7 # Default model
LLM_TIMEOUT=120 # Timeout (seconds)

Automatic BASE_URL Configuration

LLM_BASE_URLS = {
 "ZAI": "https://api.z.ai/api/coding/paas/v4",
 "OPENAI": "https://api.openai.com/v1",
 "ANTHROPIC": "https://api.anthropic.com/v1"
}

Code Structure Improvements

class Translator:
 """LLM-based translator"""

 def __init__(self):
 self.api_key = LLM_API_KEY
 self.base_url = LLM_BASE_URL # Auto-selected
 self.model = LLM_MODEL
 self.timeout = LLM_TIMEOUT

Model Configuration

Default Model

glm-4.7 (default)
max_tokens: 8192

Supported Models

Model	max_tokens
glm-4	8192
glm-4.7	8192
gpt-4o-mini	4096
gpt-4o	8192
claude-3-5-haiku	8192

Team Composition

Assembled the blog-api-server development team.

Role	Name	Responsibilities
Team Lead	team-lead	Overall management
Developer	developer	Code writing, feature implementation
Deployer	deployer	Server deployment, infrastructure
Monitor	monitor	Log analysis, performance monitoring

Server Deployment

Deployment Target

Server: blog.fcoinfup.com (130.162.133.47)
Path: /var/www/blog-api

Deployment Content

translator.py update
systemd service restart

Deployment Result

● blog-api.service - Blog API Server
 Active: active (running)

Next Steps

Translation API testing
Monitoring dashboard setup
Log file rollover policy application

Korean Version: 한국어 버전