Sentry: Tag length limit - 200 characters, shows only first, not documented

[tajchert]

• Sentry 8.18.0
• Docker

I try to log event with Android SDK (1.4.0) with tag that is over 200 characters long. I get:

"Discarded invalid value for parameter 'tags' " 
{
  "name": "tags",
  "value": [
    "test_tag_three",
    "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
  ]
}

Question is - shouldn't be max length of tag documented (also maybe client SDK should throw runtime exception/warning for such case)?
Bug - web dashboard shows only one such case for event (if event has more than one such tag it reports only first one).

[bretthoerner]

(Oops sorry about assign @mitsuhiko, ignore that.)

@tajchert We should document and warn about the tag length for sure. I don't understand your comment about the bug, though, can you provide more detail?

[tajchert]

Hi,
No problem, glad to help with pointing that out.

With bug I mean if you have 2+ more tags that are over 200 characters, only first one is displayed in web dashboard as wrongly parsed, fix would be to display all tags that are not correct/doesn't meet criteria. If this is still not clear let me know.

[bretthoerner]

Interesting, the JSON actually contains 2 errors, so I think this is a bug on the frontend.

I wonder if _.isEqual is not doing what I'd expect here: https://github.com/getsentry/sentry/blob/master/src/sentry/static/sentry/app/components/events/errors.jsx#L33

---

---

JSON:

[bretthoerner]

@macqueen this may be another easy ticket? Error data in the payload but for some reason we're only showing the user one error? My comment above shows an example -- I sent an event with 2 very large tag values.

[ethanmdavidson]

Just ran into this same issue. The error message in the web dashboard is descriptive enough that I was able to track it down easily, but it would've been nicer to have a heads up in the documentation.

Not sure if the bug mentioned in this thread is still active, as I only had one tag that violated the length requirement.

[BYK]

Ping @markstory, @untitaker

[mitsuhiko]

@BYK the error message should be more descriptive now compared to when this issue was first made. I feel like this might be resolved?

[mitsuhiko]

Current error in the UI:

Maybe still not ideal

[yuzefovich]

One easy improvement to error message could be saying exactly what the "maximum length" is, so the users could act accordingly.