Documentation: set up network metrics for Asserts

[grafsean]

Adds documentation to set up Asserts network.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.16%. Comparing base (0c7d38f) to head (fa8025a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1007      +/-   ##
==========================================
- Coverage   80.17%   80.16%   -0.01%     
==========================================
  Files         137      137              
  Lines       10930    10930              
==========================================
- Hits         8763     8762       -1     
- Misses       1685     1686       +1     
  Partials      482      482              

Flag	Coverage Δ
integration-test	55.03% <ø> (-0.12%)	⬇️
k8s-integration-test	57.60% <ø> (-0.12%)	⬇️
oats-test	37.31% <ø> (ø)
unittests	50.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[grcevski]

The test failures need a merge with main, the new jaeger release yesterday is causing us to fail to push traces.

[mariomac]

Great job!

I have a minor correction, but I'll let @gouthamve to give the final approval.

[gouthamve]

Minor nit. But LGTM!

Lets

[gouthamve]

I'd say these are optional tbh.

[grafsean]

@mariomac I forgot to tag for backports, what's the process again to manually port the change to latest?

[github-actions]

The backport to release-1.4 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-1007-to-release-1.4 origin/release-1.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x c5730ef6f72e2c4c6adaba538b9b162bd92eb516

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-1007-to-release-1.4
# Create the PR body template
PR_BODY=$(gh pr view 1007 --json body --template 'Backport c5730ef6f72e2c4c6adaba538b9b162bd92eb516 from #1007{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release-1.4] Documentation: set up network metrics for Asserts' --body-file - --label 'documentation' --label 'type/docs' --label 'backport' --base release-1.4 --milestone release-1.4 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-1007-to-release-1.4

# Create a pull request where the `base` branch is `release-1.4` and the `compare`/`head` branch is `backport-1007-to-release-1.4`.

# Remove the local backport branch
git switch main
git branch -D backport-1007-to-release-1.4