general comment
3 Topics
Architecture & GPS hardware
Hello Fabric community, I'm building a fleet monitoring platform for trucks/vehicles and need architectural guidance for using Microsoft Fabric Real-Time Intelligence, as well as GPS hardware recommendations. MY SCENARIO: ------------ - GPS trackers sending location data every 10-60 seconds via TCP - Data includes: GPS coordinates, speed, fuel level, engine RPM, temperature sensors, driver behavior (harsh braking, acceleration) - Need to support multiple tenants (each customer sees only their own fleet) - Planning to scale from 50 vehicles to 1000+ vehicles - Want real-time dashboards + historical analytics + automated alerts - Future: add video/dashcam capabilities MY PLANNED ARCHITECTURE: ------------------------ GPS Devices → TCP Server (Traccar/custom) → Azure Event Hub → Fabric Eventstream → Eventhouse → Real-Time Dashboard QUESTIONS: GPS Hardware: ------------- 1. What GPS tracker brands/models do you recommend that integrate well with custom backends and Microsoft Fabric? I'm considering Teltonika FMC920, Queclink, or Concox - any experience with these? 2. Which GPS devices have the best open protocols for parsing data and sending to Azure/Fabric? 3. Any recommendations for GPS trackers with OBD-II support to read vehicle diagnostics (fuel, RPM, error codes)? Microsoft Fabric Architecture: ------------------------------ 4. Is Eventstream + Eventhouse the right approach for high-frequency GPS telemetry data? 5. What's the recommended way to implement multi-tenancy (row-level security) for different fleet customers? 6. Should I use KQL Database or Lakehouse for storing historical GPS data (months/years)? 7. Any recommendations for handling geofencing alerts in real-time using Activator? 8. What Fabric SKU (F4, F8, F16?) would you recommend starting with for ~100 vehicles sending data every 30 seconds? I'm based in Mexico and planning to deploy this commercially for fleet owners. Any guidance from people who have built similar IoT/telematics solutions with Fabric would be greatly appreciated! Thanks in advance!Solved6.7KViews0likes4Comments
RTI Event Metadata Table Use Cases
Hi everyone, I’m looking to expand how others are using metadata tables in Microsoft Fabric RTI architectures. Current state We have an IaC-driven deployment process that provisions RTI assets from source → bronze → silver. As part of this deployment, we persist configuration and lineage information into a metadata table stored in SQL DB. At a high level, the metadata schema includes: EventTopic SourceObjectSettings (JSON) – bronze/silver table names, flatten function, etc. TopicInformation (JSON) – topic-level semantics Audit columns (create/modify user + timestamps) The metadata is written at deploy time and represents the intended RTI topology. Current primary use case: Bronze → Silver reprocessing Our main use case today is controlled reprocessing from bronze to silver. Since Fabric update policies only apply to data in motion, when we need to: fix a flattening bug handle schema changes correct downstream logic we need a way to deterministically replay historical data. To support this, I built a parameterized pipeline that accepts: EventTopic StartTime EndTime The pipeline triggers a fully parameterized notebook that: Uses the provided EventTopic to query the metadata table Retrieves the associated flatten function, bronze table, and silver table Dynamically builds the KQL query Reprocesses bronze data for the specified time window into silver This approach avoids hard-coded topic logic and has worked well so far. What I’m looking for I’m interested in learning how others are extending this metadata-driven pattern beyond reprocessing, particularly in larger RTI platforms. What other valuable use cases have you found for metadata tables in RTI architectures? Any lessons learned or pitfalls would also be appreciated. Thanks in advance.Solved7.1KViews2likes4CommentsMicrosoft Fabric Known Issues
Known issues are temporary bugs that we've discovered in Microsoft Fabric. These bugs are known and are being actively fixed. Before you submit a Support request, or search Community forums for an answer, see if the problem that you're experiencing is already known to Microsoft. There are two locations to look up current known issues: Known issues as a list on Learn Known issues as an interactive embedded Power BI report For service level outages or degradation notifications, check https://support.fabric.microsoft.com/. To create a support ticket, visit https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket.6.6KViews2likes0Comments
