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.

Sign up for GitHub

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

Jump to bottom

[otlpexporter] Add test to verify behavior on destination errors #7481

Closed
tigrannajaryan opened this issue Apr 3, 2023 · 0 comments · Fixed by #8143
Closed

[otlpexporter] Add test to verify behavior on destination errors #7481

tigrannajaryan opened this issue Apr 3, 2023 · 0 comments · Fixed by #8143
Labels
enhancement New feature or request exporter/otlp

Comments

@tigrannajaryan
Copy link
Member

We want to add tests otlpexporter to verify behavior when the destination responds with permanent and non-permanent errors.

Use the test helper after it is implemented here #7479
@tigrannajaryan tigrannajaryan changed the title [otlpexporter] Add test to verify behavior on destination errors. [otlpexporter] Add test to verify behavior on destination errors Apr 3, 2023
@tigrannajaryan tigrannajaryan mentioned this issue Apr 3, 2023
Open
@atoulme atoulme added exporter/otlp enhancement New feature or request labels Apr 13, 2023
@omrozowicz-splunk omrozowicz-splunk mentioned this issue Aug 2, 2023
Merged
dmitryax added a commit that referenced this issue Oct 24, 2023
@omrozowicz-splunk @dmitryax
[chore] add test helper to verify exporter behavior on errors (#8143)
e97ceca 
**Description:** Adding a test helper to test exporter behaviour on
errors.

**Link to tracking Issue:**
#7479
Will also fix:
#7481

It is created based on the exporter receiver test:
#7516
The exporter targets `mockReceiver` as an endpoint.

The test cases covered here are:
1. ConsumeLogs/Traces/Metrics call succeeds at the first try
2. ConsumeLogs/Traces/Metrics call fails once with non-permanent error,
then succeeds on one of the next tries
3. ConsumeLogs/Traces/Metrics call fails once with permanent error and
the data is not retried
4. ConsumeLogs/Traces/Metrics call fails once with permanent error or
permanent error (then the test pass requirement is calculated based on
number of errors per kind/successfully delivered data/total number of
data to be delivered)

---------

Co-authored-by: Dmitry Anoshin <anoshindx@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request exporter/otlp
Projects
None yet
Milestone
No milestone
2 participants
@atoulme @tigrannajaryan