We recently migrated about 450 industrial sensors and gateways to a new network segment as part of our infrastructure consolidation. Since the migration completed last week, we’re seeing a critical issue where usage data from these assets isn’t flowing to our billing dashboard.
The assets are reporting telemetry correctly and showing active status in the IoT platform, but the billing group assignments seem disconnected. When I check the asset profiles, the billing groups are still configured correctly, but usage events aren’t being forwarded to the monetization service.
I’ve verified the network connectivity and API endpoints are reachable. The monetization microservice logs show connection attempts but they’re timing out. This is impacting our ability to generate accurate invoices for our managed services customers. Has anyone encountered similar issues with billing integration after network changes?
For the bulk update, use the asset management API with a batch operation. Create a CSV mapping of asset_id to billing_group_id, then use the PATCH endpoint with the batch flag. This will update the registry without disconnecting active sessions. I’d recommend doing this during a maintenance window though, as the monetization service needs to rebuild its routing cache which takes about 10-15 minutes for that volume of assets.
Also make sure your usage event forwarding configuration is pointing to the correct monetization microservice instance. If you moved to a new network segment, the service discovery might be resolving to a different instance or load balancer endpoint. Check your IoT platform’s event routing rules - specifically the monetization_endpoint parameter in your platform configuration. We had a similar issue where events were going to a deprecated endpoint after a network change.
Thanks for the suggestion. I ran the validation query and you’re right - about 60% of the migrated assets have null billing_group_id values in the registry even though the UI shows them assigned. That explains why the usage events aren’t routing properly. Any recommendations on the best way to bulk update these references without disrupting active connections?
Good catch on the endpoint configuration. I checked and the monetization_endpoint was still pointing to the old subnet. Updated that and the routing cache is rebuilding now. Still need to fix the billing group assignments though. Going to schedule the batch update for this weekend.