Skip to content

[DOC] Remove tempo_discarded_spans_total from doc#4688

Closed
knylander-grafana wants to merge 1 commit intografana:mainfrom
knylander-grafana:ts-558-remove-internal-error-reason-doc
Closed

[DOC] Remove tempo_discarded_spans_total from doc#4688
knylander-grafana wants to merge 1 commit intografana:mainfrom
knylander-grafana:ts-558-remove-internal-error-reason-doc

Conversation

@knylander-grafana
Copy link
Copy Markdown
Contributor

What this PR does:

Removes tempo_discoarded_spans_total from doc.

Reference: #4554

Which issue(s) this PR fixes:
Fixes https://github.com/grafana/tempo-squad/issues/558

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

msg="pusher failed to consume trace data" err="rpc error: code = ResourceExhausted desc = RATE_LIMITED: ingestion rate limit (15000000 bytes) exceeded while adding 10 bytes"
```

You'll also see the following metric incremented. The `reason` label on this metric will contain information about the refused reason.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Should we replace this with anything?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

tempo_discarded_spans_total still exists. we just remove the "InternalError" reason

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Oh! My bad for misunderstanding. I'll update this doc then. This was the only place in the Tempo docs that we mentioned tempo_discarded_spans_total.

Copy link
Copy Markdown
Contributor Author

@knylander-grafana knylander-grafana Feb 14, 2025

Choose a reason for hiding this comment

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

This makes me wonder where (and if) we should document the behavior for the change or only have the change from this PR listed in release notes in the next release.

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

Labels

type/docs Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants