René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"log_struct severity isn't captured as expected","articleBody":"## What is the issue: \r\nOn using Python client library for Cloud Logging, log_struct is used to send structured logs to Cloud Logging. In structured logging, the log message and metadata are stored in Python dictionary and it is passed to the 1st argument of the method. However, the severity field is not handled as expected because severity needs to be assigned as named argument, which is not explicit from the library document.\r\n\r\n## Link to friction log: \r\nhttps://docs.google.com/document/d/19Glb2LC1jXyARXLlJbdRjY1d7I2GolCntI5hck5PuGU/edit?usp=sharing\r\n\r\n## How bad is it on a scale of 1-5 (1=Minor Annoyance; 5=Total Work Blocker)\r\n\r\n4\r\n\r\n## What were you trying to do?\r\n\r\nThis issue was originally reported by the customer (TV Asahi), and I reproduced it.\r\n\r\nI tried to send structured logs to Cloud Logging with its Python client library.\r\n\r\n##What did you expect to happen?\r\n\r\nThe 1st argument of log_struct accept the dictionary with whole metadata valid for LogEntry and handle the log severity stored in that dictionary.\r\n\r\nThat is, expecting this code:\r\n```\r\nlogdata = {\r\n    \"service\": service,\r\n    \"message\": message,\r\n    \"messageId\": context.event_id,\r\n    \"timepublished\": context.timestamp,\r\n    \"severity\": \"warning\"\r\n}\r\n\r\nvplogger.log_struct(logdata)\r\n```\r\nis treated as WARNING level log in Cloud Logging.\r\n\r\n## What actually happened?\r\n\r\nIt was treated as DEBUG level log.","author":{"url":"https://github.com/daniel-sanche","@type":"Person","name":"daniel-sanche"},"datePublished":"2021-02-18T23:08:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/190/python-logging/issues/190"}