Here are a few questions from the session (get the full Q&A deck and live recording in the #office-hours Slack channel): Q1: How do I configure the yaml for APM including any performance best practices? OpenTelemetry Collector configuration is stored in a YAML file and specifies the behavior of receivers, processors, exporters, and other components.  The Splunk Distribution of the OpenTelemetry Collector comes with a default configuration that can be modified as needed for your environment.  It can be helpful to visualize collector configuration using a tool such as OTelBin.  Documentation: Configure the Collector for Kubernetes with Helm  Collector for Linux default configuration Collector for Windows default configuration  OTelBin Q2: Can we generate a component call flow? Splunk automatically generates a service map showing the dependencies and call flow among your instrumented and inferred services in APM. The map is dynamically updated based on your selections in the time range, environment, workflow, service, and tag filters. You can use the service map to identify dependencies, performance bottlenecks, and error propagation. Documentation:  View dependencies among your services in the service map Q3: Can you cover AlwaysOn Profiling for .Net? To activate AlwaysOn Profiling, set the SPLUNK_PROFILER_ENABLED environment variable to true. To activate memory profiling, set the SPLUNK_PROFILER_MEMORY_ENABLED environment variable to true after activating AlwaysOn Profiling. Documentation:  Activate AlwaysOn Profiling (.NET) Q4: How can we get SQS to integrate into a trace for APMs? For some languages, this is included with auto-instrumentation.  For example, OpenTelemetry Java instrumentation includes support out-of-the-box for the AWS SDK, which automatically instruments calls to SQS.  You can search the OpenTelemetry registry to find details regarding SQS support with other languages.  Documentation:  https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/aws-sdk  https://opentelemetry.io/ecosystem/registry/?s=sqs&component=&language= Q6: Can you touch on API performance and availability? Create availability SLOs in o11y Cloud  Documentation:  https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/create-slo.html#measure-and-track-your-service-health-metrics-with-service-level-objectives-slos Live Questions: Q1: How do I know which attributes to use for breaking down the service map?  Blog: Up Your Observability Game with Attributes Docs: Instrument your application code to add tags to spans Docs: Filter spans within a particular trace   Q2: Do we need to set both Profiling variables for auto instrumentation as well ?  Yes.  To enable AlwaysOn Profiling with Zero config auto-instrumentation you can add the following parameters to enable CPU and memory profiling:  --enable-profiler --enable-profiler-memory Docs:  Activate AlwaysOn Profiling  Q3: Can I create customized variables and filters for APM Dashboards?  Documentation: Customize Dashboard Filters ... View more

Hey, thanks for flagging this. The domain https://experience.splunk.com will always redirect to splunk.com, but the sub-domains that include the name of the product area in the url (security, observability, platform) should all take you to the correct page.  ... View more

Hey Rich, good question! We actually built these sites on a 3rd party platform as we are working on incorporating some cool features that will make them more gamified and personalized in the future. We think this will create a more meaningful experience for our users, and we'll be sure to share these updates when they are ready. Because of that, you have to log in separately, but you should only have to one time. Please let us know if you're running into any issues! Thanks. ... View more