Splunk Enterprise Security

Splunk Enterprise Security: Adding objects to data model caused dashboards to show invalid data. Is there a way to return the data model to its "original" setup?

srunyon
New Member

I added several objects to the "Vulnerabilities" data model. After that the Enterprise Security /Security Domains/Network/Vulnerability Center dashboard started showing inconsistent values in some panels and has "search is waiting for input" on other panels. Is there a way to return the data model and the dashboard to the original configuration before I screwed them up?

0 Karma
1 Solution

mdessus_splunk
Splunk Employee
Splunk Employee

On way to do it is to go to your Splunk home directory and delete the custom files:

  • /opt/splunk/etc/apps/Splunk_SA_CIM/default/data/models/xxx.json for datamodel
  • /opt/splunk/etc/apps/xxx/local/data/ui/views/yyy.xml (or etc/users/ if they are private) for dashboards (you may use the find command if you do not know the apps they are belong too).

And you need to restart Splunk after.

View solution in original post

mdessus_splunk
Splunk Employee
Splunk Employee

On way to do it is to go to your Splunk home directory and delete the custom files:

  • /opt/splunk/etc/apps/Splunk_SA_CIM/default/data/models/xxx.json for datamodel
  • /opt/splunk/etc/apps/xxx/local/data/ui/views/yyy.xml (or etc/users/ if they are private) for dashboards (you may use the find command if you do not know the apps they are belong too).

And you need to restart Splunk after.

srunyon
New Member

Deleting the files and restarting restored the items. Thanks for the help.

0 Karma
Get Updates on the Splunk Community!

Buttercup Games: Further Dashboarding Techniques

Hello! We are excited to kick off a new series of blogs from SplunkTrust member ITWhisperer, who demonstrates ...

Message Parsing in SOCK

Introduction This blog post is part of an ongoing series on SOCK enablement. In this blog post, I will write ...

Exploring the OpenTelemetry Collector’s Kubernetes annotation-based discovery

We’ve already explored a few topics around observability in a Kubernetes environment -- Common Failures in a ...