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

Feature request: Add "Dump Reason" field when Debug is Enabled for CustomerAuth #1119

Open
MinReq opened this issue Mar 9, 2022 · 0 comments

Comments

@MinReq
Copy link

MinReq commented Mar 9, 2022

Add additional mandatory field "DUMP REASON" when enabling the dump level for customer auth

  1. IN CUSTOMERS AUTHS TABLE:
    Add Column name: DUMP REASON

Acceptance criteria: I can see DUMP REASON COLUMN inside table of /customers_auths is added after DUMP LEVEL

  1. CUSTOMERS AUTHS ID EDIT:
    Add additional mandatory field "DUMP REASON" only when "DUMP LEVEL" is enabled (changed from capture nothing to any)

Acceptance criteria:

  • I can see "DUMP REASON" in /customers_auths/{id}
  • I can see DUMP REASON in /customers_auths/{id}/edit
  • I must enter DUMP REASON when Dump level is ENABLED(changed from capture nothing to ANY other)

Scenarios:
Given I want to enable Dump level for customer auth
When I Edit Customer Auth /customers_auths/{id}/edit
And Select DUMP LEVEL = 1. Capture signalling traffic OR 2. Capture rtp traffic OR 3. Capture all traffic
Then I must enter "DUMP REASON" any plain text
And If do not enter DUMP Reason I can see error or verification "Dump reason can't be blank"

Given I want to DISABLE Dump level for customer auth
When I Edit Customer Auth /customers_auths/{id}/edit
And Select DUMP LEVEL = 1. Capture nothing
Then I can see "DUMP REASON" is not mandatory and can be left EMPTY

REASON:
When debug is ENABLED it is using server resources.
Dump Reason would help to review customer auths with dump enabled and manage them accordingly.
Also you can see a reason why it was enabled.

Thanks

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

No branches or pull requests

1 participant