CARVIEW |
Select Language
HTTP/2 200
date: Wed, 30 Jul 2025 16:39:47 GMT
content-type: text/html; charset=UTF-8
server: Apache
set-cookie: Apache=d698fa46.63b282c482b42; path=/; expires=Thu, 26-Jul-40 16:39:47 GMT; domain=.splunk.com
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
set-cookie: PHPSESSID=345f1c62488fcf3591ff06073a0be03b; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
set-cookie: ponydocs_session=345f1c62488fcf3591ff06073a0be03b; path=/; secure; HttpOnly
x-xss-protection: 1; mode=block
referrer-policy: strict-origin-when-cross-origin
Splexicon:Extend - Splunk Documentation
We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website.
Learn more (including how to update your settings) here »
extend (dataset)
extend (dataset)
verb
The act of creating a search, report, dataset, or other knowledge object that is built upon a reference to another dataset. This reference means that the object always "looks back" to the original dataset for its foundational data. If the definition of the original dataset changes, those changes are passed down to any datasets that extend it as well.
Dataset extension is not the same as dataset cloning. When you clone a dataset, you create a distinct, individual dataset that is identical to the original dataset but not otherwise connected to it. When you extend a dataset, you create a dataset, report, dashboard panel, or alert that is bound to the original dataset through its reference to that dataset.
For more information
In the Knowledge Manager Manual
A
B
C
D
E
F
I
K
L
M
P
R
S
- saved search
- scheduled alert
- scheduled report
- scheduled search
- scheduler
- scripted authentication
- scripted input
- search
- search affinity
- Search app
- search artifact
- search assistant
- search execution directive
- search factor
- search field
- search filter
- search head
- search head cluster
- search head cluster captain
- search head cluster member
- search head clustering
- search head pooling
- search head targeting
- search job
- Search Job Inspector
- search macro
- search management
- search mode
- search peer
- search peer replication
- Search Processing Language
- search scheduler
- search time
- search timeline
- search view
- searchability
- searchable
- segment
- send to background
- sequence template
- series
- server
- server class
- Settings
- SignalFlow
- SignalFx Smart Agent receiver
- Simple XML
- single-instance deployment
- single-site indexer cluster
- SmartStore
- source
- source type
- span
- span tag
- SPL
- SPL2
- SPL2 statement
- Splunk Answers
- Splunk Distribution of OpenTelemetry Collector
- Splunk OpenTelemetry Collector
- Splunk platform
- Splunk UI
- Splunk Web
- Splunk Web Framework
- Splunkbase
- splunkd
- SplunkJS Stack
- stack mode
- standalone search head
- stanza
- static captain
- streaming command
- subsearch
- summary index
T
Closing this box indicates that you accept our Cookie Policy.