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!
You forgot to mention your Traccar version.
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!