App archiving is used to present up-to-date and relevant app and add on content within Splunkbase by removing archived content from default search results. Content can be archived or reinstated as a publisher wants, contingent upon policy enforced by Splunk.
When content is archived:
- It is removed from default Splunkbase search results. Archived content is still available if a search specifically specifies the archived area of Splunkbase.
- it is categorized as "unsupported" on Splunkbase.
- publishers will not have access to leads from archived content.
On a monthly basis, content that meets all of the following criteria will be flagged by Splunk for archival:
- Compatible only with an unsupported version of Splunk. See support policy for more information, and;
- No new release has been uploaded in the prior 36 months, and;
- Content has less than 1,000 downloads.
When content is flagged for archival, the publisher will be notified by Splunk via email. The publisher can determine whether to take steps to revise the content to prevent archiving within one month.
Publisher archiving and reinstatement
A publisher can archive any owned content directly from the Manage App page for that content in Splunkbase. Likewise, for archived content, a publisher can request that any archive content should be reinstated to public status. Revised content or version compatibility information might need to be provided before content can be reinstated. For steps, see Manage content on Splunkbase.
Manage content on Splunkbase
This documentation applies to the following versions of Splunk® Answers and Splunkbase: splunkbase