Splunk Observability Cloud
Start learning about how thefollowing Observability Cloud products work to provide you with unified, end-to-end observability of your environment:
Steps Involved:
- Splunk Observability Cloud Architecture
- Get Data Into Splunk
- Splunk O11y Datatypes
- Splunk Infrastructure Monitoring
- Splunk Application Performance Monitoring (APM)
- Splunk Real User Monitoring (RUM)
- Splunk Synthetic Monitoring
- Splunk Log Observer
- Dashboarding
- Detectors
- Splunk On-Call
- Splunk Core & Olly
- Splunk Integrations
- Splunk O11y Licensing
Splunk Observability Cloud for Mobile
Splunk Observability Cloud
- Keep the context as you troubleshoot the entire stack.
- Start from Splunk RUM (frontend traces) to Splunk APM (backend traces).
- Drill deeper in Splunk Infrastructure Monitoring to identify which part of the infrastructure might be responsible for the backend error traces.
- Investigate further with codeless queries into the logs in Splunk Log Observer to see what caused the problem.
Note: Entire content is from Splunk documentation and noted important point for my own preperation purpose. Nothing else.
Step-1 : Get data in - Overview
- Integrate with cloud services to send metrics and logs
- Guided setup (AWS, Azure, GCP)
- Using API (AWS, Azure, GCP)
- Using Terraform (AWS, Azure, GCP)
- Install the OpenTelemetry Collector to send server and cluster data
- Use wizard to install (Windows, Linux, Kubernetes cluster)
- Manual installation (Windows, Linux, Kubernetes cluster)
- Configure third-party server applications to send metrics, logs, and traces
- After you’ve completed step 2. Install the OpenTelemetry Collector to send server and cluster data and installed the Splunk Distribution of OpenTelemetry Collector on your servers (hosts) or in your clusters, configure the Collector’s native receivers or any of these third-party applications, such as Apache, Cassandra, Hadoop, Kafka, and NGINX, to monitor your systems.
- Instrument back-end services and applications to send traces, logs, and metrics
- Instrument Java applications
- Instrument Python applications
- Instrument Node.js applications
- Instrument .NET applications
- Instrument Go applications
- Instrument Ruby applications
- Instrument PHP applications
- Instrument serverless functions to send traces and metrics
- Use client libraries (Same as step 7)
- Instrument user interfaces to send user sessions
- Instrument browser-based web applications for Splunk RUM.
- Instrument iOS applications for Splunk RUM.
- Instrument Android applications for Splunk RUM.
- Configure applications and serverless functions to send custom data
- Client libraries for Go
- Client libraries for Java
- Splunk distribution of OpenTelemetry Java
- Client libraries for Java
- Client libraries for node.js
- Client libraries for Python
- Client libraries for Ruby
- Use the Splunk Observability Cloud API to send custom data
- A third-party tool that provides an API/webhook integration only.
- An application written in a language we don’t provide a library for.
Step 2: Splunk Observability Features
- Create Detectors (Alerts).
- Create charts to visualize your data in dashboards & Dashboard groups to organize and share your charts.
- Custom dashboards
- Prebuilt dashboards
- Use Related Content to jump between components of Splunk Observability Cloud by clicking related data.
- Create and manage teams in Splunk Observability Cloud to coordinate team work around your data.
- Check system critical metrics, access real-time alerts, and view mobile-friendly dashboards on the go using the Splunk Observability Cloud mobile app.
- Understand Splunk Observability Cloud data model / Data types.
- Integrations (Servicenow / webhook etc)
Splunk Observability Cloud Capabilities
Splunk Observability Cloud also provides comprehensive monitoring capabilities for a wide range of application types and environments. Below is an overview of the application types that Splunk Observability Cloud can monitor:
- Web Applications
- Java applications (Spring, Tomcat, JBoss, etc.)
- .NET applications (ASP.NET, .NET Core)
- Node.js applications
- PHP applications (WordPress, Laravel)
- Ruby applications (Rails)
- Python applications (Django, Flask)
- Go applications
- JavaScript frameworks (React, Angular, Vue.js)
- Mobile Applications
- Android (Native or hybrid apps)
- iOS (Native or hybrid apps)
- Cross-platform frameworks (React Native, Flutter)
- Cloud and Microservices
- Kubernetes (GKE, EKS, AKS)
- Docker containers
- AWS services (EC2, Lambda, RDS, S3, etc.)
- Azure services (App Services, VMs, Functions)
- Google Cloud services (GKE, Cloud Functions, App Engine)
- Cloud Foundry
- OpenShift
- Server-Side Applications
- Application servers like NGINX, Apache Tomcat, IIS
- Databases (SQL and NoSQL) including MySQL, PostgreSQL, MongoDB, Oracle, Cassandra
- Enterprise Applications
- SAP (SAP HANA, ABAP)
- Oracle E-Business Suite
- Salesforce
- Microsoft Exchange
- Microsoft Dynamics
- Middleware and Messaging Systems
- Kafka
- RabbitMQ
- ActiveMQ
- IBM MQ
- Custom Applications
- Proprietary applications using OpenTelemetry, Splunk Instrumentation SDK, and custom instrumentation
- Cloud-Native and Serverless Architectures
- AWS Lambda
- Google Cloud Functions
- Azure Functions
- VMware vSphere
- APM (Application Performance Monitoring)
- End-to-end APM for APIs and microservices architecture with detailed tracing
- Monitor application flows and request tracking for REST APIs, gRPC, GraphQL, etc.
- Synthetic Monitoring
- Synthetic testing for uptime and performance monitoring of web services, APIs, and user experiences
- Observability for Containers and Orchestration
- Monitoring for containerized applications running on Kubernetes, Docker, and similar orchestration platforms.
- Log, Metrics, and Trace Correlation
- Full observability by correlating logs, metrics, and traces in real-time for troubleshooting and optimization.
Splunk Observability Cloud is well-suited for modern, cloud-native applications, with a particular focus on microservices, distributed systems, and containerized workloads. It enables monitoring across complex, hybrid environments with real-time observability into application performance, infrastructure, and user experience.
My Contact Information