Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for OpenTelemetry Community Demo Application SIG #1038

Closed
cartersocha opened this issue Apr 21, 2022 · 13 comments
Closed

Request for OpenTelemetry Community Demo Application SIG #1038

cartersocha opened this issue Apr 21, 2022 · 13 comments

Comments

@cartersocha
Copy link
Contributor

As OpenTelemetry matures, customers are increasingly looking for guides on how to onboard their services to the new paradigm or demo applications so that they can try the new tools themselves.

Multiple telemetry providers have written their own demo applications but are wholly responsible for the development & ongoing support. All of the existing demos also do not have full language coverage.

We are requesting a formal Demo Application SIG with a weekly community meeting for working on a shared community demo application.

Once approved, we'd like to have a weekly 45 min meeting on Mondays in an NA/EMEA friendly time at 0815 Pacific Time.

Project features we would like to focus on include:

  • Improving the ease of running a demo application locally while enabling it to be run on various cloud vendor platforms
  • Adding language examples for every supported OpenTelemetry language
  • Instrumenting Traces & Metrics across all languages
  • Potentially add logging support as a stretch goal
  • Ensuring the demo application is kept up to date with new OpenTelemetry features
  • Documentation to assist new customers getting onboarded to OpenTelemetry by demonstrating the full capabilities in the demo application
  • Examining the feasibility of introducing backend platform services like Azure Blob Storage, AWS DocumentDB etc.
  • Providing a load generator to simulate high frequency customer interactions

Target Personas:

  • Application owners: Installers of instrumentation.

For more details see
https://docs.google.com/document/d/1nCV32KvYzowspjWk9ym6MoLOc-1D_RF-EcX7Dnf_VcE/edit?usp=sharing

cc: @mtwo, @arminru, @aabmass, @reyang, @jsirianni

@mtwo
Copy link
Member

mtwo commented Apr 21, 2022

I support. Let's leave this up for a day or so for people to review, and then @cartersocha can create a PR to add this to the list of SIGs on the community page.

@reyang
Copy link
Member

reyang commented Apr 21, 2022

+1 I support.

@tigrannajaryan
Copy link
Member

Do you need a github repo for this SIG? We will need the repo name, and the github usernames of initial maintainers and approvers to create one.

@cartersocha
Copy link
Contributor Author

We will need one a repo once we agree on which existing demo application to start with. Then the existing app will be donated to OpenTelemetry & placed in that repo. I'll check with the channel to see what we want to call it

@austinlparker
Copy link
Member

This is a great idea! Please keep web/comms SIG in mind; We can work w/y'all to get this integrated into the QuickStarts and other docs pages (and get it featured on the site).

@ahayworth
Copy link

I think this a fantastic idea.

@nvolker
Copy link

nvolker commented Apr 25, 2022

This is awesome. Been working through the material (OTEL website, codebase examples, source code, NPM, vendor articles, etc) across multiple languages in the past 2 weeks and have really felt the itch to request something like this for ease of onboarding. Slack and pull request descriptions have been helpful in the interim, especially while feature parity discussions progress across languages.

Kudos for putting together the issue!

@arminru
Copy link
Member

arminru commented Apr 25, 2022

I added an entry for May 2nd to the public calendar since there was confusion on whether there was a meeting today or not.
@cartersocha please let me know if I should keep the 2nd or update it to the 9th.

@mtwo Please create a Google Doc from the GC Google account for us to use as the meetings notes and add it to the entry.
In the past we had meeting notes created and owned by individual's Google accounts which is not ideal.

@mtwo
Copy link
Member

mtwo commented Apr 25, 2022

Doc: https://docs.google.com/document/d/16f-JOjKzLgWxULRxY8TmpM_FjlI1sthvKurnqFz9x98/edit

@cartersocha
Copy link
Contributor Author

@tigrannajaryan our maintainers / approvers are as follows:
Maintainers: myself (@cartersocha), @mtwo, @austinlparker, & waiting for confirmation from @arminru if he has the bandwidth.
Approvers: @reyang, @mic-max, @jsirianni, & @julianocosta89

Repo name: opentelemetry-demo-webstore

@tigrannajaryan
Copy link
Member

Repo created https://github.com/open-telemetry/opentelemetry-demo-webstore and approvers/maintainers added.

@lizthegrey, @bogdandrutu EasyCLA action does not show up in the main branch protection: https://github.com/open-telemetry/opentelemetry-demo-webstore/settings/branch_protection_rules/25424445

Anything I need to do to enable it?

@cartersocha
Copy link
Contributor Author

Merged 💯 #1046

@tigrannajaryan
Copy link
Member

@lizthegrey, @bogdandrutu EasyCLA action does not show up in the main branch protection: https://github.com/open-telemetry/opentelemetry-demo-webstore/settings/branch_protection_rules/25424445

I tried again and now I can see it. Enabled. All good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants