You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 others would be good to have documented?
The text was updated successfully, but these errors were encountered: