Pieter Hagedoorn
05/28/2025, 1:40 PMgrpcurl -plaintext \
-d '{"key":"message1", "arguments":["argument1","argument2"]}' \
-proto AuditServiceV1.proto \
-import-path target/protoc-dependencies/ec4b3d39b9b3c3f5186cf878d88e0a4e/nl/bkwi/specification/proto \
-H "X-correlation-id: 1" -v\
localhost:8088 nl.bkwi.audit.log.grpc.v0100.AuditLog_v0100Service/AuditLogRequest
Resolved method descriptor:
rpc AuditLogRequest ( .nl.bkwi.audit.log.grpc.v0100.AuditLogRecord ) returns ( .nl.bkwi.audit.log.grpc.v0100.AuditLogResponse ) {
option (.google.api.http) = { post: "/AuditLog_v0200/AuditLogRequestV2" };
}
Request metadata to send:
x-correlation-id: 1
Response headers received:
content-type: application/grpc
grpc-status-name: OK
matched-stub-id: 5e78e4f5-d7b9-4dd6-8e90-3bd1b7e84b29
matched-stub-name: aanroep splunk geeft 200 OK
Response trailers received:
(empty)
Sent 1 request and received 0 responses
ERROR:
Code: ResourceExhausted
Message: grpc: received message larger than max (577594739 vs. 4194304)