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

Documenting "enterprise" concerns #1309

Open
cartermp opened this issue Apr 22, 2022 · 0 comments
Open

Documenting "enterprise" concerns #1309

cartermp opened this issue Apr 22, 2022 · 0 comments
Labels
discussion Input from everyone is helpful to drive this forward docs e2-days Effort: < 5 days

Comments

@cartermp
Copy link
Contributor

We semi-regularly see enterprise users have scenarios that go far beyond the "getting started" stuff we have documented today, or their version of "getting started" is either more complex or required plugging OTel into a particular workflow.

To that end, it's probably a good idea to collect some things we've seen from enterprise users (or potential users) and see if there's a set of concerns we can get documented.

Some examples:

  • What's the best way to use OTel with Spring, specifically?
  • How do I consider rolling out automatic instrumentation across a fleet of 500 services?
  • How do I scrub sensitive data so I don't have a privacy oopsie?
  • How do I drop noisy data so my vendor costs aren't bananas?
  • How do I drop a subset of data, like useless known frames of a captured track trace in a recorded exception?
  • Are there some architecture diagrams I can look at to get a sense for how to instrument?
  • How do you keep the concept of API keys per env/team/project when using a centralized OTel Collector Gateway?

What others would be good to have documented?

@cartermp cartermp added docs e2-days Effort: < 5 days labels Jul 9, 2022
@svrnm svrnm added the discussion Input from everyone is helpful to drive this forward label Sep 8, 2022
@svrnm svrnm removed the discussion Input from everyone is helpful to drive this forward label Jan 18, 2024
@theletterf theletterf added the discussion Input from everyone is helpful to drive this forward label Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Input from everyone is helpful to drive this forward docs e2-days Effort: < 5 days
Projects
None yet
Development

No branches or pull requests

3 participants