1. Telemetry & Data Acquisition
FoxCloud OpenAPI
Vpp Flow
  • Vpp Flow
  • Full API Reference
  • What's New & Milestones
  • Getting Started
    • 1. Overview & Integration Scope
    • 2. Environments & Prerequisites
  • End-User Enrollment & OAuth Flow
    • 0. Introduction
    • 1. The User Authorization Journey
    • 2. OAuth Token Operating Model
    • 3. Implementation Guide
  • API Technical Specifications
    • 1. Universal Request Rules
    • 2. Rate Limiting Strategy
    • 3. Response Structure
    • 4. Error Code Reference
  • Telemetry & Data Acquisition
    • 1. Data Pipeline & Scaling Strategy
    • 2. Telemetry Data Query (Real-time)
    • 4. Telemetry Variable Dictionary
    • 5. System Performance & SLA
    • 3. Device Configuration & Settings: Pre-Dispatch State Awareness
  • Control Commands & Dispatch
    • 1. Core Dispatch Architecture: Scheduler V3
    • 2. Scheduler V3 Operations
    • 3. Real-time Device Settings
    • 4. Strategic Roadmap: Scaling for Massive Fleets
  • FAQ
    • Troubleshooting Quick Guide
  1. Telemetry & Data Acquisition

5. System Performance & SLA

This section defines the technical performance boundaries of the FoxCloud platform. Please take these metrics into account when designing your VPP's data processing architecture and retry mechanisms.

6.1 Key Performance Metrics#

MetricSpecificationNotes
Kafka Message TTL3 DaysRetention period for messages in the Kafka queue. If your consumer is down for more than 7 days, data will be lost.
Kafka Push Frequency~5 MinutesStandard batch interval for telemetry data pushed to Kafka.

6.2 Rate Limiting Recap#

For comprehensive rate limiting rules (Daily Quota per Client ID and Frequency Limits per Interface), please refer to API Technical Specifications: 3. Rate Limit Strategy section.
Modified at 2026-07-21 08:22:58
Previous
4. Telemetry Variable Dictionary
Next
3. Device Configuration & Settings: Pre-Dispatch State Awareness
Built with