Uploaded image for project: 'Ansible Automation Platform RFEs'
  1. Ansible Automation Platform RFEs
  2. AAPRFE-1609

Provide the ability for customer-defined tags for errors and patterns

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • automation-analytics
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Background

       

      User Stories

      Provide the ability for customer-defined tags for errors and patterns. This would allow standard errors and patterns already defined within Automation Analytics, but in addition allow creation and of customer-defined patterns as well. Additionally, provide a dashboard that allows grouping, viewing, and reporting using those customer-defined tags. Examples of some errors could be "Variable not defined”, “UI Issue”, and “Timeout”.

      Supporting documentation

      Initial completion during New status and then remove this blue text.

      <include links to technical docs, diagrams, etc>

      Definition of Done

      Initial completion during Refinement status and then remove this blue text. 

      Should be reviewed and updated by the team, based on each team agreement and conversation during backlog refinement.

      < REPLACE AND COPY FROM THIS GUIDANCE DOC>

      • Apply customer-defined tag for that error or pattern reported by Automation Analytics.
      • Access customer-defind grouping, viewing, and reporting using those customer-defined tags.

      Acceptance Criteria

      COPY THIS INTO THE ACCEPTANCE CRITERIA FIELD during New status and then remove this section. 

      Requirements

      <Replace these with the functional requirements to deliver this work>

      • Review error or pattern as reported in Automation Analytics
      • Apply customer-defined tag for that error or pattern in Automation Analytics.
      • Access customer-defind grouping, viewing, and reporting using those customer-defined tags.

      End to End Test

      <Define at least one end-to-end test that demonstrates how this capability should work from the customers perspective>

      1. Review error or pattern as reported in Automation Analytics
      2. Apply customer-defined tag for that error or pattern in Automation Analytics.
      3. Access customer-defind grouping, viewing, and reporting using those customer-defined tags.

      If the previous steps are possible, then the test succeeds.  Otherwise, the test fails.

              Unassigned Unassigned
              rhn-support-asanders Andrew Sanders
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: