[SPIKE] Investigate content-build monitoring and auditing logs to gather a set of datapoints that should be collected for next-js

[nfpappas-oddball]

User Story or Problem Statement

As a data viewer, I want to see the same data being reported from next-js as is currently reported from content-build so that I can maintain a consistent data-set

Acceptance Criteria

• We have document with the minimum data-points

[nfpappas-oddball]

I have looked at datadog for content build. It has reviled the following fields:
- archive duration
- broken link count
- build duration
- graphql pages

• build steps (assets)
• build steps (content assets)
• build steps (drupal prefix)
• build steps (add_filenames_for_debugging)
• build steps (add permalinks fooindex)
• build steps (filename dates)
• build steps ( apply layouts - various)
• build steps ( static files)
• build steps ( check collections)
• build steps (drupal debug page)
• build steps (create environment filter)
• build steps (create header and footer)
• build steps (outreach assets data)
• build steps (create resouces of the website)
• build steps (create sitemap)
• build steps (download assets)
• build steps ( drupal assets)
• build steps ( genreate navigation)
• build steps (drupal content)
• build steps ( group collections)
• build steps ( ignore assets for build)
• build steps ( virtual dom)
• build steps (content into templats)
• build steps ( nav menu levels)
• build steps ( rewrite drupal pages)
• build steps ( rewrite domains)
• build steps (translate markdown to html)
• build steps (update robots.txt)
  - build steps ( deploy duration)
• build steps ( header violations)
• build steps ( total file violations)
• build steps ( total violations)
  - build steps ( overall duration)
  - build steps ( setup duration)

In bold are the recommended metrics that we keep. An over-whelming majority of these metrics seem auto-generated. In bold is ones that are specifically being populated in the content-release.yml runner deployment.

I believe that there are no other metrics due to the fact that any other fields such as active connections would be stored in amazon.