Clearblade writing logs with resource.type=”cloudiot_device” become invalid?

[AlanZSS]

Quote from Clearblade ticket response: 

"We recently started getting a warning from Logs Explorer of an invalid resource type: “cloudiot_device”. This resource type has been used for a long time and only started being flagged as invalid very recently. It seems this may explain what you are seeing: the LOGS going to Logs Explorer are being blocked. 
The resource type “cloudiot_device” is still listed as a supported one here however, as I mentioned earlier, recently it started being flagged as an “invalid type”. We have not gotten a response from Google as to why the change."

We depends on this log from Clearblade IoT core(kind of official alternative to GCP IoT core) to update our device's status(online/offline).  It was the same mechanism even before the GCP IoT Core retired.

This change causing system wide status incorrect. Could you please help or explain with this ASAP Thanks.

[sacha · Accepted solution]

FYI, ClearBlade have also raised this as an incident - see here

[AlanZSS]

I had known that before the announcement. The issue from Clearblade was filed by us.
This change of the deprecation of the resource type ="cloudiot_device" on the GCP Logging should have a notice on the release note, but there is none. This caused a major impact on our reliability toward our customers and, at the same,  us toward GCP.

[skysharma]

@sacha I see cloudiot_device is still listed in this doc:
https://cloud.google.com/logging/docs/api/v2/resource-list

Should it be removed?

[sacha]

I'm not a Google representative, but since Google Core IoT was shut down, I would assume so?