docs(logging): add write log entry sample

[MukundaKatta]

Fixes #15426.

Adds a handwritten Cloud Logging sample for the logging_write_log_entry region tag that demonstrates:

• writing a textPayload entry
• writing a jsonPayload entry
• severity, labels, and global monitored resource metadata
• single-entry writes and batched writes

Tested:

• /private/tmp/google-cloud-python-logging-venv/bin/python -m pytest packages/google-cloud-logging/samples/snippets/write_log_entry_test.py

[snippet-bot]

Here is the summary of changes.

You are about to add 1 region tag.

• packages/google-cloud-logging/samples/snippets/write_log_entry.py:24, tag logging_write_log_entry

---

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

[gemini-code-assist]

Code Review

This pull request introduces a new Python sample and corresponding unit tests for writing text and structured log entries to Google Cloud Logging. The review feedback focuses on improving the code's robustness and adherence to library best practices, specifically by importing from the public API surface, using the client's helper method for log path construction, and adding basic command-line argument validation to prevent runtime errors.

[gemini-code-assist]

Avoid importing from deep internal paths like services.logging_service_v2 or types. It is more idiomatic and robust to import from the public surface of the library, which is less likely to change in future versions.

Suggested change

	from google.cloud.logging_v2.services.logging_service_v2 import LoggingServiceV2Client
	from google.cloud.logging_v2.types import LogEntry
	from google.cloud.logging_v2.types import WriteLogEntriesRequest
	from google.cloud.logging_v2 import LoggingServiceV2Client
	from google.cloud.logging_v2 import LogEntry
	from google.cloud.logging_v2 import WriteLogEntriesRequest

[gemini-code-assist]

Instead of manually constructing the log resource name string, use the log_path helper method provided by the client. This ensures the name is correctly formatted and follows the library's best practices.

Suggested change

	log_name = f"projects/{project_id}/logs/python-example-log"
	log_name = client.log_path(project_id, "python-example-log")

[gemini-code-assist]

The script will raise an IndexError if no command-line argument is provided. Adding a simple check for sys.argv improves the usability of this sample by providing a clear usage message.

Suggested change

	if __name__ == "__main__":
	write_log_entry(project_id=sys.argv[1])
	if __name__ == "__main__":
	if len(sys.argv) < 2:
	print("Usage: python write_log_entry.py <PROJECT_ID>")
	sys.exit(1)
	write_log_entry(project_id=sys.argv[1])

[parthea]

Hi @MukundaKatta,

Thanks for opening a PR. Regrettably, samples for google-cloud-logging have moved to https://github.com/GoogleCloudPlatform/python-docs-samples/tree/main/logging/samples/snippets . I'm going to close this PR but please feel free to open a new PR in https://github.com/GoogleCloudPlatform/python-docs-samples.