Splunk Search

splunk event identifier

dordavid
Explorer

hey there 🙂 

i'm trying to make a table with the next fields: name, last name and message:

index a | table name last name message

i want to add the identifier of event to my table - (the identifier which splunk generate (c_id?) )

how can i done that?

 

Labels (2)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @dordavid,

what do you mean with: "the identifier which splunk generate (c_id?)"?

what do you want to do with it?

Ciao.

Giuseppe

0 Karma

dordavid
Explorer

hey @gcusello 
i want to create one big table:

index=a | table name last name message

i want to drill down to another hidden table:

when i will click on the message value -> an hidden panel will be seen with a table that show the only the chosen raw.

i want to drill down with a query like:

 index=a  identifier=???? | table name last name message

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @dordavid,

there isn't an absolute identifier because the events depend on the search.

So you could pass in drilldown all the fields in your table: name last_name message.

something like this:

        <drilldown>
          <link target="_blank">/app/your_app/drilldown_dashboard?name=$row.name$&amp;last_name=$row.last_name$&amp;message=$row.message$</link>
        </drilldown>

Ciao.

Giuseppe

0 Karma

dordavid
Explorer

@gcusello 

 usually my message field is very long - sometimes 150 rows length, so i used substr function on my message field, so actually my my message seems like:
eval message=substr(message, 1, 1000) - (only first 1000 chars)

 

i want to click on the message value  and display an hidden panel will show a table with the chosen raw.  

i try to do:

message=$row.message$

but sometimes i got errors like: "unbalanced quotes" - [because of the substr].

so i think to use _cd of event to do the search

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @dordavid,

as I feared, there are some quotes in your message, so you can't use it.

See if the other two fields are enough, otherwise you have to take another one in order to uniquely identify the event on which to drill down, a field that you can then also not display (using the <fields> option) at the end.

Ciao.

Giuseppe

0 Karma
Get Updates on the Splunk Community!

CX Day is Coming!

Customer Experience (CX) Day is on October 7th!! We're so excited to bring back another day full of wonderful ...

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...