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
Copy file name to clipboardExpand all lines: docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/sumo-logic-kickstart-data-source.md
+30-29Lines changed: 30 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Kickstart Data comes preloaded for new trial users and expires automatically aft
24
24
| :--- | :--- |
25
25
| Initial Data | The source ingests data from 6 hours in the past and 6 hours into the future. |
26
26
| Regular Ingestion | Every 6 hours, the source ingests an additional 6 hours of future-dated data to ensure dashboards are always populated. |
27
-
| Latency Spike Simulation | The data demonstrate a scenario showcasing latency spikes, aiding in performance analysis and debugging. |
27
+
| Latency Spike Simulation | The data demonstrates a scenario showcasing latency spikes, aiding in performance analysis and debugging. |
28
28
29
29
## Setup
30
30
@@ -34,50 +34,51 @@ The Kickstart Data source is automatically included when you create a new organi
34
34
35
35
## Kickstart Data availability and cleanup
36
36
37
-
Kickstart Data is preloaded in all new Sumo Logic trial accounts to help you explore the platform without needing to ingest your own data. This sample data powers dashboards, log searches, and alerts using simulated application logs.
37
+
Kickstart Data is preloaded in all new Sumo Logic Trial accounts to help you explore the platform without needing to ingest your own data. This sample data powers dashboards, log searches, and alerts using simulated application logs.
38
38
39
39
Kickstart Data is streamed continuously throughout your trial. As a result, the total volume of sample data will grow daily unless you manually stop the collector.
40
40
41
-
note... In some cases, the Kickstart collector may remain active beyond the 7-day period originally expected. Be sure to manually delete the collector to fully stop data ingestion.
41
+
:::note
42
+
In some cases, the Kickstart collector may remain active beyond the 7-day period originally expected. To stop ingestion entirely, you must delete the collector manually.
43
+
:::
42
44
43
-
### How to remove Kickstart Data
45
+
### How to manage or remove Kickstart Data
44
46
45
-
You can wait for Kickstart Data to expire automatically at the end of your trial, or remove it manually at any time by following the steps below:
47
+
If you want to prevent Kickstart Data from continuing to ingest or appearing in your searches, you can choose from the following options.
46
48
47
-
#### Step 1: Delete the Kickstart Collector (recommended/≥≤)
49
+
#### Delete the Kickstart collector (recommended)
48
50
49
-
1. In Sumo Logic, go to **Manage Data > Collection**.
50
-
2. Locate the collector named `sample_otel_astronomy_shop`.
51
-
3. Delete the collector to stop Kickstart Data ingestion.
51
+
To stop new Kickstart Data from being ingested every 6 hours:
52
52
53
-
#### Step 2: Reduce retention on Kickstart partition
53
+
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic top menu, select **Configuration**, and then under **Data Collection**, select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.
54
+
1. Locate the collector named `sample_otel_astronomy_shop`.
55
+
1. Delete the collector.
54
56
55
-
1. Go to the **Partitions** page (see [Edit the Retention Period](/docs/manage/partitions/manage-indexes-variable-retention/#edit-the-retention-period) for guidance).
56
-
2. Locate the partition named `sample_otel_astronomy_shop`.
5. Wait at least 24 hours for the data to be aged out.
57
+
This action prevents further sample data from entering your account.
60
58
61
-
#### Step 3 (Optional) Adjust the default partition
59
+
#### Filter Kickstart Data out of search results (optional)
62
60
63
-
In some cases, a small amount of Kickstart Data may end up in the default partition `sumologic_default`.
61
+
To focus only on your own data in search, use a filter to exclude Kickstart logs by metadata.
64
62
65
-
:::caution
66
-
Only proceed if you're certain you haven’t started ingesting your own logs, as this will remove **all** data in the default partition.
67
-
:::
63
+
Add a line like the following to your query:
64
+
65
+
```sql
66
+
_sourceCategory !="kickstart"
67
+
```
68
+
69
+
You can also filter by other metadata such as `_sourceName` or `application`, depending on your environment. Kickstart logs often include tags like `application="astronomy-shop"`.
70
+
71
+
Use this method if you prefer not to delete the collector or change any partition settings.
68
72
69
-
1. While still on the **Partitions** page, locate the partition named `sumologic_default`.
70
-
2. Edit the retention period and set it to **1 day**.
71
-
3. Click **Apply change now**.
72
-
4. After 24 hours, restore your preferred retention setting by returning to the partition settings and increase the retention back to your preferred duration (e.g., 30 days) to preserve ongoing ingested data.
### Known issue: Retention change may not fully remove old data
75
+
While it is technically possible to remove Kickstart Data by [reducing the retention period](/docs/manage/partitions/manage-indexes-variable-retention/#edit-the-retention-period), we do not recommend this method for most users:
75
76
76
-
Some users have reported that Kickstart Data remains in their account even after retention is reduced and 24+ hours have passed. Engineering is actively investigating this behavior. If you're still seeing older data:
77
+
* Lowering retention to 1 day may still take up to 3 days to fully remove data.
78
+
* Changing retention on the `sumologic_default` partition can result in permanent loss of your own logs.
79
+
* Creating new partitions and routing rules requires advanced knowledge of metadata and configuration.
77
80
78
-
- Double-check that the partition retention was applied and saved correctly.
79
-
- Confirm that the collector has been deleted to stop new data from arriving.
80
-
- Reach out to [Support](https://support.sumologic.com/support/s) if the issue persists.
81
+
Instead, we recommend deleting the collector and using search filters to isolate your data.
0 commit comments