René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"*Breaking* changes to the default logging resource type","articleBody":"We have been using this client to write stackdriver logs for a 2-3 years. Those logs have been written as a `global` resource type. \r\n\r\nWe have Stackdriver logging sinks exporting those logs to a Pub/Sub topic, with sink filters for the resource.type (among other things). Another application is collecting those logs for analytics.\r\n\r\nWe redeployed the application with the latest client a few days ago, and the aforementioned Pub/Sub topic stopped receiving messages. I just tracked it down to a change in behavior in this client (we didn't notice it at first, and when we did tracking it down was difficult).\r\n\r\nLogs from the current client are now logging stored with a resource.type of `k8s_container`.\r\n\r\nIt looks like the change is in this PR https://github.com/googleapis/python-logging/pull/200\r\n\r\n#### Steps to reproduce\r\n\r\n  1. Run the code below using google-cloud-logging==2.2.0 in GKE\r\n  2. Upgrade google-cloud-logging to 2.3.0\r\n  3. Run the code in GKE again\r\n  4. Notice the resource.type changes from `global` to `k8s_container`\r\n\r\n#### Code example\r\n\r\n```python\r\nimport google.cloud.logging\r\n\r\nclient = google.cloud.logging.Client(project='test-project')\r\nlogger = client.logger('test-log')\r\nlogger.log_struct(dict(foo='bar'))\r\n```\r\n\r\nThe resource.type is indexed in cloud logging, and used in possibly every example log filter in the google docs. I have to believe others will be affected by this breaking change.\r\n\r\nSee, for example: https://cloud.google.com/logging/docs/view/advanced-queries","author":{"url":"https://github.com/jceresini","@type":"Person","name":"jceresini"},"datePublished":"2021-03-23T05:02:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/233/python-logging/issues/233"}