connectors
6 TopicsArchitecture & 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.7KViews0likes4CommentsWeb Connector for Customer Web API
Is anyone familiar with the OAuth2 handshake between Power BI's "Web" connector and the AAD? I have a customer with a proprietary web api. The API can be changed as needed to perform the oauth2 handshake that generates an access token for use by the Power Query import. But no matter what we do, the handshake is not being performed correctly. The web api starts by properly generating the HTTP 401 WWW-AUTHENTICATE, and that gets us pretty far. But the error we are getting from Power Query is very problematic: "invalid_resource / resource principal was not found in the tenant". See image: For some reason the "Web" connector is not very flexible, and requires a strict resource URI. It always expects to use a rigid one that is based on the HTTP address: IE. see docs https://docs.microsoft.com/en-us/power-query/connectorauthentication "Power Query would expect your Application ID URL value to be equal to https://api.myservice.com." I guess in our example, the resource URI that it is probably requiring is http://localhost (not https://api.myservice.com). But we don't wan't to use a URI that is based on the HTTP address. If there are any Power BI experts who are familiar with the Oauth2 handshake which is used for the "Web" connector, I would greatly appreciate some feedback. Side note: The inflexibility of this Oauth2 handshake is pretty problematic by itself. To make matters even worse, the Microsoft AAD is now requiring resource URI's to be in a "verifiedCustomDomain". See https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-breaking-changes#appid-uri-in-single-tenant-applications-will-require-use-of-default-scheme-or-verified-domains This gives me little hope that a local IIS Express API would work (hosted on "http://localhost"). How can we connect the Power BI "Web" connector to a local web service that is actively under development? if anyone has AAD tips, they would be appreciated as well.Solved4.2KViews0likes3Commentswe are not able to connect direct query in power bi report server by using starrocks connector
Hi Team we have StarRocks.mez file(Power bi custom connector) with this custom connector we are able to connect direct query in Power BI Report Server Desktop application, but after publish report in ReportServer we are not able open the report getting below error message Tested with SQLServer as well got the same error in power BI Report server, but after adding environment variable connecting to SQLServer issue got resolved in report server So tried the same with StarRocks connection by adding environmental variable but issue still issue exists Can any one please help on this?1.5KViews0likes2CommentsIn the power BI Network Navigator visualization, how do I add a text field value as a link label?
In the power BI Network Navigator visualization, how do I add the value in a “notes and keywords” field as link text for the link between nodes? I have a field called "Notes and keywords" that explains why any two nodes are connected. How do I add the text from this field to the connector, preferably as a mouseover? Thanks!!!!