Skip to content

Conversation

@simvlad
Copy link
Contributor

@simvlad simvlad commented Jan 6, 2026

What changed?

Added a new counter event_blob_size_error, which is bumped every time the payloads size (BlobSizeLimitError) or memo size (MemoSizeLimitError) is crossed.

Why?

Currently we do not have a specific metric monitoring blob size errors and ErrBlobSizeExceedsLimit error that is thrown is serviceerror.NewInvalidArgument, which is aggregated with other errors of that kind.

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

Potential risks

Any change is risky. Identify all risks you are aware of. If none, remove this section.

@simvlad simvlad requested review from a team as code owners January 6, 2026 20:50
@simvlad simvlad requested review from jmaeagle99 and yycptt January 6, 2026 20:50
"event_blob_size_error",
WithDescription("The number of requests that failed due to blob size exceeding limits configured with BlobSizeLimitError and MemoSizeLimitError."),
)
HeaderSize = NewBytesHistogramDef("header_size", WithDescription("The size of the header in bytes passed to the server by the client. This metric is experimental and can be removed in the future."))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Should the spacing be restored so it lines up most of the other metric definitions? Or did the formatter remove the extra space?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants