Device-Level forward.url vs Global forward.url for Large-Scale Deployments
You forgot to mention your Traccar version.
We are using the traccar versoin 4.10
That's an ancient version that definitely doesn't support this feature.
Thank you for the confirmation, Anton.
We are planning to upgrade to the latest version. As a workaround for now, we're considering using a global forward.url.
Our deployment has more than 10,000 devices, with devices reporting every 10–30 seconds while moving. From a scalability and performance perspective, would using a single global forward.url have any significant impact on the Traccar server, or is that the recommended approach until we upgrade?
Thanks in advance for your guidance.
It will definitely have a significant impact. Forwarding can be slow, depending on the latency to your service.
Ok, thank you for the confirmation.
Do you know from which version onward device-level forwarding is supported?
No. You would need to check git history.
Hi,
We are using JSON forwarding and have a requirement to forward position data to different endpoints based on the device.
We tried configuring forward.url as a device attribute along with forward.enable=true and forward.url=URL, but it seems that only the global forward.url from traccar.xml is being used. If the global forward.url is not configured, forwarding fails with:
URI template of the newly created target must not be null
Is forward.url at the device level supported, or is only the global forward.url expected to work?
We have a deployment with more than 10,000 devices. Each device reports frequently while moving, and we also need to process Bluetooth (iBeacon/EYE Sensor) data and maintain the latest beacon packet in our backend.
From a scalability and production perspective, would you recommend using a single global forwarding URL and routing requests in the backend based on the device, or is there a better approach for deployments of this size?
Thanks!