Create base template for search query schema going to collect

[luisgmetzger]

Problem

Currently, we are logging some data to collect service but we are missing some useful data from the service source and schema fields from the request itself that we can use collect service to collect.

How did we discover this problem?

Job Story(s)

When client makes fetch request, I would like to log request fields along with service request using collect service and have files for this in S3.

What are we planning to do about it?

1. Integrate collect service more into fetch service.

What are we not planning to do about it?

How will we measure success?

Security Considerations

Required per CM-4.

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.

Based on our current data collect meeting with these notes:

https://docs.google.com/document/d/1fMZIrMUJCNz74vc7UPOy3GzMBUHBP1QyypxT0kjdxX8/edit?usp=sharing

We need to create an initial base schema for search queries being done for a domain that will go to collect service.

[jadudm]

1. Add fetch logging (or did we just do that?)
2. Add search logging to API

so we can do a crawl and then do some perf testing on the API?