Reporting

default.meta - auto-generated while errors by App Inspect

altink
Builder

Hello

At the AppInspect Report generated at splunkbase for my app: Omega Core Audit I can see the following errors:

 

check_meta_file_parsing
.............
Duplicate stanza at line 231 in [views/oca_unf_aud_trail] of default.meta. File: metadata/default.meta Line Number: 231
Duplicate stanza at line 235 in [views/oca_dashboard] of default.meta. File: metadata/default.meta Line Number: 235
.............


check_validate_no_duplicate_stanzas_in_meta_files
.............
Duplicate [views/oca_dashboard] stanzas were found. File: metadata/default.meta Line Number: 235

Duplicate [views/oca_unf_aud_trail] stanzas were found. File: metadata/default.meta Line Number: 146
.............

 



The issue here is:
the default.meta is a file that has been fully maintained by Splunk. I have not touched it manually.

Question 1:
How is possible that something fully handled by Splunk is reported as an error by a Splunk Tool (App Inspect)?
Question 2:
How can I fix these? In case of the need to remove duplicates - which one from a couple (or more) should I delete?

best regards
Altin

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!

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...

Splunk Brings Proof of Control to Digital Asset Transfers

Digital assets now sit inside the core of financial services. HSBC launched its Tokenized Deposit Service in ...

Manage Ingest Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Ingest Processor pipeline, deploy it to the ...