使用托管在Google基础架构上的可靠，多对多的异步消息传递来连接您的服务。 Cloud Pub / Sub会根据您的需要自动扩展，并为构建您自己的强大全球服务奠定基础。
为什么GCP Pubsub PublishMessage如此慢
当我测试它时，
我正在尝试实现的情况： 我写了一份Benthos作业，该作业从酒吧/子订阅者中摘下消息，使用该数据调用两个API，并为每个故障发送Slack警报。最后，如果在调用两个API时遇到任何错误，则该消息未被确认。
当我通过Pub/Sub Subscriber收到消息时，我正在尝试触发云功能。该订户正在呼吁另一个项目（我可以在项目中查看消息）。但是现在，我需要触发一个云功能以消耗消息。
您无法在项目B中的PubSub主题上的项目A中插入云功能。您需要部署HTTP功能并创建推送订阅以调用该功能。
用码头容器中创建pub/sub和log stink的issue
(deploy-functions) kernal42@space42 KT % podman run --rm -v /Users/kernal42/Downloads/my-project-anp-c94dc8530044.json:/app/key.json:ro --env=GOOGLE_APPLICATION_CREDENTIALS=/app/key.json localhost/rtsink:latest INFO:root:Creating topic: projects/my-project-anp/topics/kt-test-local-15 INFO:root:Topic created: projects/my-project-anp/topics/kt-test-local-15 ERROR:root:Sink not found: projects/my-project-anp/sinks/kt-test-local-15 Traceback (most recent call last): File "/app/main.py", line 41, in setup_pubsub_logsink existing_sink = config_client.get_sink(request={"sink_name": sink_path}) File "/usr/local/lib/python3.10/site-packages/google/cloud/logging_v2/services/config_service_v2/client.py", line 2199, in get_sink response = rpc( File "/usr/local/lib/python3.10/site-packages/google/api_core/gapic_v1/method.py", line 131, in __call__ return wrapped_func(*args, **kwargs) File "/usr/local/lib/python3.10/site-packages/google/api_core/retry/retry_unary.py", line 293, in retry_wrapped_func return retry_target( File "/usr/local/lib/python3.10/site-packages/google/api_core/retry/retry_unary.py", line 153, in retry_target _retry_error_helper( File "/usr/local/lib/python3.10/site-packages/google/api_core/retry/retry_base.py", line 212, in _retry_error_helper raise final_exc from source_exc File "/usr/local/lib/python3.10/site-packages/google/api_core/retry/retry_unary.py", line 144, in retry_target result = target() File "/usr/local/lib/python3.10/site-packages/google/api_core/timeout.py", line 130, in func_with_timeout return func(*args, **kwargs) File "/usr/local/lib/python3.10/site-packages/google/api_core/grpc_helpers.py", line 78, in error_remapped_callable raise exceptions.from_grpc_error(exc) from exc google.api_core.exceptions.NotFound: 404 Sink kt-test-local-15 does not exist INFO:root:Creating sink: kt-test-local-15 INFO:root:Created new sink with writer identity: serviceAccount:[email protected] INFO:root:getting the iam policy for the sink: projects/my-project-anp/sinks/kt-test-local-15 ERROR:root:Error setting up pubsub and logsink: 403 User not authorized to perform this action. Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/google/api_core/grpc_helpers.py", line 76, in error_remapped_callable return callable_(*args, **kwargs) File "/usr/local/lib/python3.10/site-packages/grpc/_channel.py", line 1181, in __call__ return _end_unary_response_blocking(state, call, False, None) File "/usr/local/lib/python3.10/site-packages/grpc/_channel.py", line 1006, in _end_unary_response_blocking raise _InactiveRpcError(state) # pytype: disable=not-instantiable grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.PERMISSION_DENIED details = "User not authorized to perform this action." debug_error_string = "UNKNOWN:Error received from peer ipv4:142.250.193.202:443 {grpc_message:"User not authorized to perform this action.", grpc_status:7, created_time:"2025-02-15T05:19:05.783737357+00:00"}" > The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/app/main.py", line 98, in <module> setup_pubsub_logsink(PROJECT_ID, TOPIC_NAME, SINK_NAME) File "/app/main.py", line 68, in setup_pubsub_logsink policy = publisher.get_iam_policy(request={"resource": topic_path}) File "/usr/local/lib/python3.10/site-packages/google/pubsub_v1/services/publisher/client.py", line 1940, in get_iam_policy response = rpc( File "/usr/local/lib/python3.10/site-packages/google/api_core/gapic_v1/method.py", line 131, in __call__ return wrapped_func(*args, **kwargs) File "/usr/local/lib/python3.10/site-packages/google/api_core/grpc_helpers.py", line 78, in error_remapped_callable raise exceptions.from_grpc_error(exc) from exc google.api_core.exceptions.PermissionDenied: 403 User not authorized to perform this action. (deploy-functions) kernal42@space42 KT %
以pub/sub -google cloud Platform
我有一个主题，与酒吧/sub的订阅有关。 我想通过VSCODE在本地测试我的函数，尤其是当消息发布在我的主题上时触发的功能。
根据此网页的符合条件，可以在云中的实例上触发CLI的PubSub事件
gcloud pubsub topics publish topic-name --message '{"name":"Xenia"}'
pub/sub (golang) 当负载峰值时 /ModifyAckDeadline 出现许多 InvalidArgument 错误
在高负载期间，10 分钟内创建了约 9000 条消息，我们观察到消息处理存在问题。某些 pod（通常是一两个）始终返回以下错误...
跨 GCP 项目的 Google 实时开发者通知和 PubSub
是否可以跨GCP项目订阅pubsub通知？ 我们希望为生产和测试环境设置实时开发人员通知，以处理来自 Google 的应用内购买
如果 GCP pub sub 订阅过期时间与订阅消息保留时间相同，订阅不会过期
我们有一个 GCP pub sub 订阅，其过期时间设置为 1 天，而消息保留期限也设置为 1 天。 订阅里没有消息但还没过期...