V2 HHT — PIPELINE DASHBOARD

v2-hht-azure | 4.0  ·  Central India  ·  P1V2
LIVE
Updated just now
PIPELINE FLOW
LAYER 1
Android HHT
v12.098 · Zebra TC-series
Active HTTPS
LAYER 2
Azure App Service
v2-hht-api · P1V2 · Central India
Checking…
LAYER 3
Azure Relay HC
java-mw-9080 · Service Bus
1 Listener TUNNEL
LAYER 4
Server 200 · Java
192.168.144.200:9080 · Tomcat/JCo
Checking…
LAYER 5
SAP S/4HANA
192.168.144.185 · Client 600
Responding
LAYER 6
CDN · R2
assets.eatnubo.com · APK
26.9 MB 200 OK
TOTAL RFC CALLS
Since last restart
AVG LATENCY
Azure→SAP roundtrip
SUCCESS RATE
Infrastructure errors
ACTIVE / REGISTERED
— / 117
never-called: loading…
persist: checking…
BOTTLENECKS — SLOWEST RFCs (avg ms) Avg latency
Loading…
LIVE RFC FEED — LAST 15 CALLS Live
Loading…
OPCODE PERFORMANCE TABLE — ALL RFCs
OPCODE CAT CALLS ERRORS AVG ms MIN ms MAX ms P95 ms LATENCY PROFILE
Loading…
OPTIMISATION OPPORTUNITIES
Response Caching Layer
Cache read-only RFC responses in Azure Memory Cache. Opcodes like storegetbin_v2, packgingmaterial, zwm_store_get_major_cat return near-static data. 60-second TTL would cut SAP load by ~40% during rush hours.
⬆ HIGH IMPACT — 40% fewer SAP calls
🔄
HC Proxy IP Pre-warm
App Service restarts force a full 127.0.0.x scan (4s cold start). Store the discovered HC proxy IP in Azure App Settings and update it via a Cloudflare Worker health-check every 5 minutes. Eliminates cold-start latency spike on restart.
⬆ HIGH IMPACT — eliminates 4s cold start
📊
Per-Store Error Alerting
Route App Insights logs to a Cloudflare Worker that parses [HHT] lines and sends WhatsApp alerts when a specific store has >10 consecutive errors — indicates a connectivity or device issue at that store before staff escalate.
⬆ HIGH IMPACT — proactive monitoring
🗜️
Response Compression
Large opcodes like storegetbin_v2 return 2-4KB of bin codes over HTTPS. Enable GZIP on the Azure App Service. On 1000 devices making ~20 calls/day this saves ~160MB/day in cellular data — matters for stores on 4G dongles.
→ MED — bandwidth savings on 4G stores
🔀
Parallel RFC Fan-out
Dashboard screens call 2-3 SAP RFCs sequentially. Middleware can detect multi-opcode requests (comma-separated) and fire them in parallel, returning combined response. Example: login screen needs scnrec + storegetbin_v2 — both can run simultaneously.
→ MED — faster screen loads
📱
Auto-APK Push via HC
When a new APK is deployed to CDN, push a silent notification to all connected devices via a Cloudflare Worker → Azure Event Grid → HC → Java middleware broadcast. Devices auto-download in background instead of waiting for next login.
↗ LOW — nice to have for 1000-device rollout
CLOUDFLARE WORKERS — AUTOMATION LAYER
hht-health-monitor
Cron every 5 min → hits /api/hht/health → parses Java status + latency → updates KV store → sends WhatsApp via n8n if Java unreachable for >2 consecutive checks. Auto-detects HC IP shift and updates App Setting.
⏱ cron: */5 * * * *
hht-stats-aggregator
Cron every 15 min → hits /api/hht/stats → parses opcode table → writes to D1 database with timestamp → builds 7-day history of latency trends per RFC. Powers weekly performance report to your WhatsApp.
⏱ cron: */15 * * * *
hht-apk-publisher
GitHub webhook → on new release tag → download APK from GitHub → upload to R2 → update appversion response → send WhatsApp to store managers with download link. Fully automated zero-touch APK distribution pipeline.
→ github webhook trigger
hht-rate-limiter
Cloudflare WAF rule + Worker: limit each device IP to 600 req/min (10 rps). Blocks runaway retry loops that could flood SAP. Returns E#Too many requests — Android app handles this gracefully with 2s backoff.
→ WAF + Worker combo
hht-rfc-cache
Worker intercepts read-only opcodes (storegetbin_v2, packgingmaterial, zwm_store_get_major_cat) → checks KV cache → returns cached response within 1ms if fresh → falls through to Azure if stale. 60s TTL per store.
→ KV cache layer
hht-log-forwarder
Scheduled Worker reads App Insights → parses [HHT] structured logs → writes daily CSV to R2 → sends summary to your email/WhatsApp every morning: top 5 slowest RFCs, stores with most errors, total call volume by hour.
⏱ cron: 0 7 * * * (7am IST)
AZURE APP SERVICERunning
PlanP1V2 Premium
RegionCentral India
Runtime.NET 4.8 / Windows
App Insights90d retention
HC Tunneljava-mw-9080 ✓
SAP Pool50 / 300 peak
ANDROID APKv12.098
Version12.098
APK Size26.9 MB
Default ServerAzure Prod ✓
Volley Timeout90,000ms
Upgrade Modeforce
CDNassets.eatnubo.com ✓
SERVER 200 · SAPOn-prem proxy
Server192.168.144.200
OSWindows Server 2012
RoleJava/JCo proxy only
SAP Host192.168.144.185
SAP Client600 / SysNum 02
UserBATCHUSER