Skip to content

Commit 6f694e3

Browse files
authoredApr 17, 2024··
Update End User Resources (#4286)
1 parent b0713c8 commit 6f694e3

File tree

7 files changed

+88
-68
lines changed

7 files changed

+88
-68
lines changed
 

‎.htmltest.yml

+2
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,8 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
3535
- ^https://x.com
3636
# OTel Google calendar - curl returns 200, but the link checker gets a 401:
3737
- ^https://calendar.google.com/calendar/embed\?src=google.com_b79e3e90j7bbsa2n2p5an5lf60%40group.calendar.google.com
38+
# YouTube playlists sometimes give a 404, although they give a 200 when accessed via browser:
39+
- ^https://www.youtube.com/playlist\?list=
3840

3941
# Ignore Docsy-generated GitHub links for now
4042
- ^https?://github\.com/.*?/.*?/(new|edit)/ # view-page, edit-source etc
+32-25
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,33 @@
11
---
2-
title: End-user Resources
3-
linkTitle: End User
4-
description: Vendor-agnostic resources for users of OpenTelemetry
2+
title: End-user resources
3+
linkTitle: End user
4+
description: Vendor-agnostic resources for OpenTelemetry users
55
---
66

7-
The [OpenTelemetry End User Working Group][] has heard feedback from users who
8-
desire a vendor-agnostic space to discuss adopting OpenTelemetry, so we provide
9-
multiple ways for you to connect with other users of the project and share best
10-
practices:
11-
12-
- [A synchronous monthly discussion group](discussion-group/)
13-
- [A private slack channel](slack-channel/)
14-
- [Talks about OTel in practice](otel-in-practice/)
15-
- [Direct interview/feedback sessions](interviews-feedback/)
16-
17-
These forums will bring together operations and development engineers from
7+
Looking to connect with other OpenTelemetry end users in a vendor-agnostic
8+
space, or to learn more about OpenTelemetry? Perhaps you have some feedback
9+
about your implementation or adoption that you'd like to share with project
10+
contributors, or you want to help prioritize project issues. You've come to the
11+
right place!
12+
13+
- To connect with other end users and learn about upcoming events:
14+
- Join the [Slack channel](slack-channel/)
15+
- Join the [APAC end user discussion group](discussion-group/)
16+
- To learn about OpenTelemetry, check out:
17+
- [OTel in practice](otel-in-practice/)
18+
- Curated content on the
19+
[OpenTelemetry YouTube channel](https://www.youtube.com/@otel-official)
20+
- To provide feedback and help prioritize issues:
21+
- Participate in a [direct interview/feedback session](interviews-feedback/)
22+
- Take a [survey](/community/end-user/feedback-survey/)
23+
- Join a panel discussion (more info coming soon!)
24+
- Vote on issues (more info coming soon!)
25+
26+
These forums aim to bring together operations and development engineers from
1827
different organizations to discuss challenges and solutions to achieving
19-
ubiquitous observability. Share successes and failures, discover best practices,
20-
and meet others who are also on a journey to implement observability powered by
21-
OpenTelemetry.
28+
ubiquitous observability. We encourage you to share your successes and failures,
29+
discover best practices, and meet others who are also on a journey to implement
30+
observability powered by OpenTelemetry.
2231

2332
### Topics
2433

@@ -37,15 +46,13 @@ But here are some of the kinds of things we expect will be on the table:
3746

3847
**Is this group only for OpenTelemetry end users?**
3948

40-
No! Anyone is welcome to join and discuss their journey to observability. This
41-
group is hosted by the OpenTelemetry Community End-User Working Group, so we
42-
expect most participants will be from organizations that are evaluating or using
49+
Everybody is welcome to join and discuss their journey to observability. This
50+
group is hosted by the OpenTelemetry Community End-User SIG, so we expect most
51+
participants will be from organizations that are evaluating or using
4352
OpenTelemetry.
4453

4554
**I have questions about this, who can I reach out to?**
4655

47-
You can find members of the End User Working Group in
48-
[#otel-user-research](https://cloud-native.slack.com/archives/C01RT3MSWGZ).
49-
50-
[opentelemetry end user working group]:
51-
https://github.com/open-telemetry/community/tree/main/working-groups/end-user
56+
You can find members of the
57+
[OpenTelemetry End User SIG](https://github.com/open-telemetry/community/tree/main/working-groups/end-user)
58+
in [#otel-sig-end-user](https://cloud-native.slack.com/archives/C01RT3MSWGZ).

‎content/en/community/end-user/discussion-group.md

+5-13
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,9 @@ description: Monthly OpenTelemetry usage discussions, all are welcome!
55
weight: 20
66
---
77

8+
**As of April 2024, AMER and EMEA sessions are discontinued in favor of
9+
discussion panels with a more targeted focus.**
10+
811
Interested in learning how other end users are implementing OpenTelemetry in
912
their organizations? Come talk shop with other OpenTelemetry end users! This is
1013
a vendor-neutral space to discuss best practices, ask questions, and meet other
@@ -16,7 +19,6 @@ and changes to the project.
1619

1720
## About
1821

19-
- Sessions are available for all regions!
2022
- Search the blog for "End-User Discussions" to find summaries of past
2123
discussions.
2224
- A project maintainer and/or a Governance Committee member will be in
@@ -29,21 +31,11 @@ and changes to the project.
2931
Here are upcoming sessions, or you can view them on the
3032
[OpenTelemetry calendar](https://github.com/open-telemetry/community#calendar):
3133

32-
- **EMEA (Europe, Middle East, and Africa)**: every third Tuesday of the month
33-
at 11AM GMT ([Zoom link](https://us06web.zoom.us/j/85691064809?pwd=c0VCejh))
34-
- February 20
35-
- March 19
36-
- April 16
3734
- **APAC (Asia Pacific)**: every third Wednesday of the month at 11AM India ST
3835
(GMT +5.5), [register](https://lu.ma/1w129wgu) to get the Zoom link
39-
- February 21
40-
- March 20
4136
- April 17
42-
- **AMER (Americas)**: every third Thursday of the month at 9AM PT (GMT -8),
43-
([Zoom link](https://us06web.zoom.us/j/87037874951?pwd=WGo3eUZpeWFZTlhJQXhJeXZhQmwvUT09))
44-
- February 15
45-
- March 21
46-
- April 18
37+
- May 15
38+
- June 19
4739

4840
Past topics/questions have included:
4941

‎content/en/community/end-user/interviews-feedback.md

+15-12
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ description: Help improve OpenTelemetry - share your feedback directly with us!
44
weight: 10
55
---
66

7-
One of the core functions of the OpenTelemetry End User Working Group is to
8-
improve the project by gathering feedback from end users and sharing them with
9-
the appropriate SIGs to help drive prioritization of improvements and changes to
10-
the project.
7+
One of the core functions of the OpenTelemetry End User SIG is to improve the
8+
project by gathering feedback from end users and sharing them with the
9+
appropriate SIGs to help drive prioritization of improvements and changes to the
10+
project.
1111

1212
Direct interview or feedback sessions between an organization and the
1313
OpenTelemetry Community is one such resource. In these hour-long sessions, we
@@ -24,8 +24,8 @@ We will then take the feedback you shared and turn them into actionable tasks
2424
for the relevant SIGs, as well as provide context and insight for you during the
2525
session as appropriate.
2626

27-
We schedule these sessions once a month, usually during one of the end-user
28-
working group's meetings (alternating Thursdays at 10AM Pacific Time), but can
27+
We try to schedule these sessions once a month, usually during one of the
28+
end-user SIG's meetings (alternating Thursdays at 10AM Pacific Time), but can
2929
set up a different time if that does not work for you. The sessions are
3030
typically attended by a few project maintainers and/or Governance Committee
3131
members, as well as some curious general members of the Community.
@@ -40,13 +40,16 @@ Things to keep in mind:
4040
concerns.
4141
- These are open to the public, so other users may come and ask you questions.
4242

43-
To schedule a session, reach out to us in
44-
[CNCF Community Slack](https://communityinviter.com/apps/cloud-native/cncf):
43+
You can view
44+
[past recordings](https://www.youtube.com/playlist?list=PLVYDBkQ1TdywIl9xKEo5_u7zlwY38dW43)
45+
on the OpenTelemetry YouTube channel.
46+
47+
To schedule a session, reach out to us via
48+
[CNCF's Community Slack](https://communityinviter.com/apps/cloud-native/cncf):
4549

4650
- In the
47-
[#otel-user-research](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
51+
[#otel-sig-end-user](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
4852
channel
4953
- Via direct message: ping
50-
[Reese Lee](https://cloud-native.slack.com/team/U03UARAJ405),
51-
[Adriana Villela](https://cloud-native.slack.com/team/U02EUCBFK8A), or
52-
[Rynn Mancuso](https://cloud-native.slack.com/team/U03FU45JA1M)
54+
[Reese Lee](https://cloud-native.slack.com/team/U03UARAJ405) or
55+
[Adriana Villela](https://cloud-native.slack.com/team/U02EUCBFK8A)

‎content/en/community/end-user/otel-in-practice.md

+13-10
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
2-
title: OpenTelemetry In Practice
2+
title: OTel In Practice
33
linkTitle: OTel in Practice
44
description: >-
5-
_OpenTelemetry in Practice_ is a _series_ of talks initiated by some members
6-
of the End User Working Group.
5+
_OTel in Practice_ is a _series_ of talks initiated by some members of the End
6+
User SIG.
77
weight: 30
88
---
99

@@ -14,13 +14,16 @@ We’re aiming to:
1414
- Build stronger connections with developers focused on specific languages
1515
- Improve the experience of implementing OpenTelemetry in production
1616

17-
Each OpenTelemetry in Practice session will include a half hour of lightning
18-
talks and a half hour of open conversation about the topic. We are looking for
19-
people to join the OpenTelemetry in Practice team and people to give talks at
20-
future events. So if you’re interested in shaping these conversations, reach out
21-
in the
22-
[#otel-user-research channel](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
23-
of the [CNCF Slack](https://slack.cncf.io).
17+
Each OTel in Practice session typically includes one or more talks by end users
18+
or project contributors, with space for discussion. We welcome speakers from all
19+
backgrounds! If you're interested in sharing what you've learned in a 15-minute
20+
lightning talk or a longer 30-minute session, reach out in the
21+
[#otel-sig-end-user channel](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
22+
on the [CNCF's Slack](https://slack.cncf.io).
23+
24+
You can view
25+
[past sessions](https://www.youtube.com/playlist?list=PLVYDBkQ1TdyxKgdGE4ThYLkNRCuLLYy9x)
26+
on the OpenTelemetry YouTube channel.
2427

2528
Join the
2629
[OpenTelemetry in Practice Meetup Group](https://www.meetup.com/opentelemetry-in-practice-meetup-group/)

‎content/en/community/end-user/slack-channel.md

+17-8
Original file line numberDiff line numberDiff line change
@@ -2,19 +2,28 @@
22
title: Slack Channel
33
linkTitle: Slack
44
description: >-
5-
Join a private slack channel to discuss OpenTelemetry with other end users.
5+
Join a Slack channel to discuss OpenTelemetry with other end users.
66
weight: 40
77
---
88

9-
- Confirm your agreement with channel [Code of Conduct][] and reach out to Reese
10-
Lee, Rynn Mancuso, or Adriana Villela on CNCF slack for an invite to
11-
`#otel-endusers`.
9+
Previously, we had a private channel to provide a space for end users to discuss
10+
adoption and implementation issues while allowing them to maintain a layer of
11+
privacy and to meet compliance concerns. Now that the project and community have
12+
grown, and with the transition of the End User WG to End User SIG, we believe
13+
that this private channel is no longer needed.
14+
15+
As of April 2024, we will begin shifting all of our communications to the
16+
[#otel-sig-end-user](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
17+
channel (previously named the #otel-user-research channel), and will be
18+
archiving the private channel by April 30, 2024.
19+
20+
We encourage you to join us over at #otel-sig-end-user to learn about our new
21+
charter, what you can expect from us as an end user, and more. Note the
22+
following:
23+
1224
- Troubleshooting or tactical SDK specific questions are still best directed to
1325
individual SIG channels or the
1426
[#opentelemetry](https://cloud-native.slack.com/archives/CJFCJHG4Q) channel.
1527
- Vendor specific questions are still best directed to vendor channels, or if it
16-
doesn’t exist
28+
doesn’t exist,
1729
[#otel-vendor](https://cloud-native.slack.com/archives/C031SAMGV2A)
18-
19-
[code of conduct]:
20-
https://github.com/open-telemetry/community/blob/main/working-groups/end-user/discussion-group-code-of-conduct.md

‎static/refcache.json

+4
Original file line numberDiff line numberDiff line change
@@ -8883,6 +8883,10 @@
88838883
"StatusCode": 200,
88848884
"LastSeen": "2024-01-30T16:34:02.591185-05:00"
88858885
},
8886+
"https://www.youtube.com/@otel-official": {
8887+
"StatusCode": 200,
8888+
"LastSeen": "2024-04-15T11:38:45.271323+02:00"
8889+
},
88868890
"https://www.youtube.com/embed/coPrhP_7lVU": {
88878891
"StatusCode": 200,
88888892
"LastSeen": "2024-01-30T16:15:42.688406-05:00"

0 commit comments

Comments
 (0)
Please sign in to comment.