Splunk Mission Control

Splunk ES Notables Not Flowing into Mission Control

kevinmabini
Engager

Hello,

We have PROD and DEV instance that are both running Mission Control with the following versions below:
PROD - ES v7.1.1, Mission Control v3.0.2
DEV - ES v7.3.0, Mission Control v3.0.2

PROD works fine and incidents are tally between ES and MC. Unfortunately for DEV, some of the notables from ES are not flowing into MC. 

Is this an issue with the latest version of ES? I've looked into the latest release notes of both ES and MC, and it's not listed in the "Known Issues" page. Can't find anything helpful too in the internal logs.

Any insights will be highly appreciated. Thank you!

Labels (1)
Tags (1)
0 Karma

phanTom
SplunkTrust
SplunkTrust

Just checking that the correlation searches are the same across the env and they all have the "Create Notable" and "Create Mission Control Incident" Adaptive responses?

0 Karma

seaaan
Splunk Employee
Splunk Employee

Hi Kevinmabini, the ingestion flow should not be affected by the upgrade. Could you open a support case? So that we can then take a close look at the stack and identify the issue. Thanks!

0 Karma
Get Updates on the Splunk Community!

The OpenTelemetry Certified Associate (OTCA) Exam

What’s this OTCA exam? The Linux Foundation offers the OpenTelemetry Certified Associate (OTCA) credential to ...

From Manual to Agentic: Level Up Your SOC at Cisco Live

Welcome to the Era of the Agentic SOC   Are you tired of being a manual alert responder? The security ...

Splunk Classroom Chronicles: Training Tales and Testimonials (Episode 4)

Welcome back to Splunk Classroom Chronicles, our ongoing series where we shine a light on what really happens ...