Observability: Application Performance Monitoring (APM): Session 1 - 3/20/24

adepp — Wed, 17 Apr 2024 21:32:18 GMT

Register here. This thread is for the Community Office Hours session on Observability: Application Performance Monitoring (APM) on Wed, March 20, 2024 at 1pm PT / 4pm ET.

This is your opportunity to ask questions about your current Observability APM challenge or use case, including:

Sending traces to APM
Tracking service performance with dashboards
Setting up deployment environments
AutoDetect detectors
Enabling Database Query Performance
Setting up business workflows
Implementing high-value features (Tag Spotlight, Trace View, Service Map)
Anything else you'd like to learn!

Please submit your questions at registration or as comments below. You can also head to the #office-hours user Slack channel to ask questions (request access here).

Pre-submitted questions will be prioritized. After that, we will open the floor up to live Q&A with meeting participants.

Look forward to connecting!

Re: Observability: Application Performance Monitoring (APM): Session 1 - 3/20/24

adepp — Wed, 17 Apr 2024 21:39:04 GMT

Here are a few questions from the session (get the full Q&A deck and live recording in the #office-hours Slack channel):

Q1: Since when has the evolution of Splunk APM started & why is it that companies are starting to realize the benefit of it very late

We’ve been doing this since the beginning - it just wasn’t called Observability!
Splunk APM launched in 2020
Now recognized in the Leaders Quadrant in the Gartner Magic Quadrant for APM
Join us at .conf24 to learn about new capabilities, see product demos, and more!

Q2: Can you show the latest method of Otel Installation and Instrumentation?

Opt into auto instrumentation with the OpenTelemetry Collector installation (Java, Node.js, .NET): Demo

Documentation:

Q3: How do I understand which microservice is having an issue?

Docs: Investigating the root cause of an error with the Service Map
Lantern: Implementing Distributed Tracing
Blog: How to investigate a reported problem
Lantern: Troubleshooting a service latency issue related to a database query
Lantern: Using Business Workflows in Splunk APM

Q4: Can I have some guidance for monitoring AKS environments?

Other questions from the session (solutions in the #office-hours Slack channel):

What is the best practice for enabling APM on an app running in Azure App Service as a Java Web App?
What do we mean by troubleshooting metrics vs. monitoring metrics?
I'm starting from scratch for my team to instrument our microservices and lambdas with otel in golang.
Does Splunk Observability Cloud have a dependency on Splunk Enterprise/Cloud? Or is it an independent product?
Can we still ingest logs directly to Splunk Observability cloud?
How SOC is licensed? I expect we can now ingest only Metrics n Traces
Does the “Splunk OpenTelemetry Collector for Kubernetes” (Helm chart) support sending telemetry to Splunk APM and logs to Splunk Enterprise at the same time?
What is the best practice for instrumenting services running as an App Service in Azure? I've seen some stellar documentation covering ECS and K8s use cases but I'm a little unsure what the best process is for Azure App Services.
How does Splunk Observability link services between APM and Infrastructure?
Is this demonstration with custom instrumentation? Could you show an example with custom code instrumentation, for example with attributes / custom metrics
Can I write custom queries for the traces I ingest? For the purposes of debugging, alerting, reporting, etc.
How is a service different from Business workflow? Is BW collection of services?

rss.livelink.thread@place:occasion

Observability: Application Performance Monitoring (APM): Session 1 - 3/20/24

Re: Observability: Application Performance Monitoring (APM): Session 1 - 3/20/24