Feature: Examples with profiling

[xBlaz3kx]

Proposed changes

• Newest LGTM image includes Pyroscope, exposed it
• Added k6 for performance testing
  • K6 performance metrics will be pushed to Prometheus, so they can be queried via Grafana directly
• Added profiling to examples

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

• I have read the CONTRIBUTING doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
did and what alternatives you considered, etc...

[coveralls]

Pull Request Test Coverage Report for Build 17362171832

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 4 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.2%) to 87.136%

---

Files with Coverage Reduction	New Missed Lines	%
ws/websocket.go	4	84.78%

Totals
Change from base Build 17354791705:	-0.2%
Covered Lines:	718
Relevant Lines:	824

---

💛 - Coveralls