Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processor doc: add description for queued processor #454

Merged
merged 1 commit into from
Jan 15, 2020

Conversation

huikang
Copy link
Member

@huikang huikang commented Dec 10, 2019

Signed-off-by: Hui Kang [email protected]

@codecov-io
Copy link

codecov-io commented Dec 10, 2019

Codecov Report

Merging #454 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #454   +/-   ##
=======================================
  Coverage   76.16%   76.16%           
=======================================
  Files         122      122           
  Lines        7574     7574           
=======================================
  Hits         5769     5769           
  Misses       1534     1534           
  Partials      271      271

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 21a70d6...c9d078b. Read the comment docs.

Copy link
Contributor

@rghetia rghetia left a comment

Choose a reason for hiding this comment

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

one minor comment. LGTM otherwise.

receiver or previous processor to the next span processor. On
receiving trace data, the queued processor produces items to the queue. At the
same time, the queued processor has one or more workers which consume the trace
data in the queue by sending them to the next span processor.
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe add some description about retry logic?

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated. Thanks for your feedback.

Copy link
Contributor

@pjanotti pjanotti left a comment

Choose a reason for hiding this comment

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

Thanks @huikang, some small suggestions to the text.

processor/README.md Outdated Show resolved Hide resolved
processor/README.md Outdated Show resolved Hide resolved
processor/README.md Outdated Show resolved Hide resolved
processor/README.md Outdated Show resolved Hide resolved
processor/README.md Outdated Show resolved Hide resolved
processor/README.md Outdated Show resolved Hide resolved
@huikang
Copy link
Member Author

huikang commented Dec 14, 2019

@pjanotti , updated. Thanks for the suggestions.

Received trace data is enqueued immediately if the queue is not full . At the
same time, the processor has one or more workers which consume the trace
data in the queue by sending them to the next processor. On failure of
consuming the trace data, the processor retries after some backoff delay
Copy link
Member

Choose a reason for hiding this comment

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

Unclear what "consuming" refers to. Maybe say instead: "If relaying the trace data to the next processor or exporter in the pipeline fails ..."

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated. Thanks.

@pjanotti pjanotti merged commit 18bbe32 into open-telemetry:master Jan 15, 2020
MovieStoreGuy pushed a commit to atlassian-forks/opentelemetry-collector that referenced this pull request Nov 11, 2021
…try#454)

* Drop entry from correlation map

Entry used to contain stuff like TTL, but right now the notion of
entry was dropped from the spec.

* Compute exact size of the correlations map

The map will be immutable, so spend some more time to ensure that we
will not unnecessarily waste some memory on a basically read-only map.

* Allow dropping keys from correlations map

This is to follow the spec. Before this change it was possible in an
awkward way by using Foreach to gather and filter the key-value pairs,
and then calling NewMap with a MultiKV MapUpdate.

* Document the correlation package

* Add missing license blurbs in correlation package

* Add tests for deleting items in correlations

* Factor out getting map size and test it

This is an implementation detail that can't be tested in a black-box
manner.

* Fix copyright dates

* Simplify/disambiguate keySet function parameters/return values

* Fix typo in Apply docs

* Fix test names

* Explain the nonsense of dropping keys from new map
hughesjj pushed a commit to hughesjj/opentelemetry-collector that referenced this pull request Apr 27, 2023
…y#454)

Bumps [boto3](https://github.com/boto/boto3) from 1.17.85 to 1.17.88.
- [Release notes](https://github.com/boto/boto3/releases)
- [Changelog](https://github.com/boto/boto3/blob/develop/CHANGELOG.rst)
- [Commits](boto/boto3@1.17.85...1.17.88)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.

6 participants