Set up Splunk Observability Cloud components 🔗
See Welcome to Splunk Observability Cloud for a description of each component in Observability Cloud. With the exception of Log Observer Connect, you must send data from your systems to each Observability Cloud component. You do not need to send your Splunk Cloud Platform or Splunk Enterprise logs to Observability Cloud to analyze them in Log Observer Connect. Instead, see Set up Log Observer Connect for Splunk Cloud Platform or Set up Log Observer Connect for Splunk Enterprise to run the native integration that allows you to analyze your Splunk platform logs in Log Observer Connect without sending them outside of your Splunk platform instance.
For every Observability Cloud component, see the following topics to send your data to Observability Cloud:
Set up Splunk APM to send traces to Splunk APM.
Set up Infrastructure Monitoring to send infrastructure data to Splunk Infrastructure Monitoring.
Set up Log Observer Connect for Splunk Cloud Platform to view and analyze your Splunk Cloud Platform logs in Log Observer Connect. (Setup is required, but your logs do not leave your Splunk Cloud Platform instance.)
Set up Log Observer Connect for Splunk Enterprise to view and analyze your Splunk Enterprise logs in Log Observer Connect. Setup is required, but your logs do not leave your Splunk Enterprise instance.
Set up Splunk RUM for mobile and browser applications to send front-end traces and spans, as well as user session data to RUM. By default, RUM does not collect identity data.
Set up Splunk Synthetic Monitoring to set up your first Uptime and Browser tests.
Set up Splunk Incident Intelligence to configure alerts, incident policies, and on-call schedules in Incident Intelligence.
For an overview of setting up all components and the suggested order of setup, see Get data into Splunk Observability Cloud.