Splunk Search

Combining two different events with same values from different source types

gvjyothi45
New Member

index=a0_payservutil_generic_app_audit_prd sourcetype="npp:pom:stdout" eventCode="fundsReservationManualInterventionNeeded"

 

index=prod_payments OR index=a0_payservutil_generic_app_audit_prd sourcetype="npp:cbis:techevent" $selected_ID$ | rex mode=sed field=_raw "s/\x1f/|/g"

| eval fields=split(_raw,"instructionReceiptIdentification=")

| eval RN=mvindex(fields,1)

| eval Recp=split(RN, "'")

| eval ReceiptNumber=mvindex(Recp, 2)

| eval EntityID=mvindex(Recp, 6)

|dedup ReceiptNumber

|table _time, ReceiptNumber, EntityID

 

The above two queries i am having it. First query identify the entity id which is having 'manualinterventionneeded' and second query get the receipt number by using that entity id. Entity ID in first query and instructionReceiptIdentification in second query having the same values. By matching these two values i want to get one query to create an alert.

 

Could you please help me on this ?

Labels (6)
0 Karma

diogofgm
SplunkTrust
SplunkTrust

First combine both queries:

(index=a0_payservutil_generic_app_audit_prd sourcetype="npp:pom:stdout" eventCode="fundsReservationManualInterventionNeeded") OR (index=prod_payments OR index=a0_payservutil_generic_app_audit_prd sourcetype="npp:cbis:techevent" $selected_ID$) 


Then you need to combine the 2 fields from both searches into one. Then use the coalesce function to fill an ENTITY field with the values of first valid following the order inside function. This should be placed after any eval or regex used to extract these fields.

| eval ENTITY = coaalesce(EntityID, instructionReceiptIdentification)

 

------------
Hope I was able to help you. If so, some karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...