Investigate work needed for other OpenSearch subtasks

[bofstein]

• Talk to the other team members that have implemented OpenSearch
• Make more of a determination of what we need for initial configuration
• Get more precise estimate of work for other subtasks

[jupiter007]

Did some research into how to create a Dashboard in OpenSearch.

I saved some data off of the ezid index patterns, and then created visualizations for them and added them to my test dashboard juliet-viz-test.

Here's a screenshot:

When researching, I used existing index patterns. I don't know who created those, and didn't create my own, but I know where I can when the time comes.

We will want to make sure that our logs contain:

• status_codes (500 errors, 400 errors, 300 codes, etc)
• A function field that will help us track what activities are happening on what parts our site
• error type field, like Forbidden, Bad User Input, Unauthorized, etc.
• latency and response times
• error rate
• total requests
• response times

[briri]

Terry shared the following code snippets:

• Lograge gem
• Lograge config
• Code for writing directly to or Querying OpenSearch - this might be useful in the new tool

The setup within the DMPTool should be straightforward. We can use Terry's example with a few modifications. See the Lograge docs for handling things like multiple base controllers.