Knowledge Management

Is there any way to limit the number of search results in a data model?

emiliavanderwer
Explorer

When searching on an index, you can pipe to "head 100" and retrieve 100 results.

index=my_index cookie* | head 100

However, when searching over a data model, how do you tell it to get only 100 results?

| tstats count from datamodel=my_dm where g.message=cookie* by g.id

0 Karma
1 Solution

renjith_nair
Legend

@emiliavanderwerf,

Did you try

| tstats count from datamodel=my_dm where g.message=cookie* by g.id|head 100

Below works for me

|tstats count from datamodel=test by sourcetype|head 2

Where test is index=_internal

---
What goes around comes around. If it helps, hit it with Karma 🙂

View solution in original post

woodcock
Esteemed Legend

The exact same way:

| tstats count from datamodel=my_dm where g.message=cookie* by g.id | head 100

Or, more productively,

| tstats count from datamodel=my_dm where g.message=cookie* by g.id | sort 100 - count

renjith_nair
Legend

@emiliavanderwerf,

Did you try

| tstats count from datamodel=my_dm where g.message=cookie* by g.id|head 100

Below works for me

|tstats count from datamodel=test by sourcetype|head 2

Where test is index=_internal

---
What goes around comes around. If it helps, hit it with Karma 🙂
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...