Managing New Relic Public Site Search
Overview
This guide documents how to manage and optimize search functionality across New Relic's public sites and the NR1 Help Center feature. Search is a critical component for customer experience, supporting everything from technical support ticket deflection to in-product help discovery.
Search Architecture
New Relic uses Swiftype, an Elasticsearch-based search engine, to power search functionality across all public sites. The architecture includes:
- Admin UI: Web interface for managing the search engine configuration
- Site Crawler: Automated system for indexing website pages
- REST API: Programmatic interface for managing indices and fetching results
- Unified Engine: Single Swiftype engine indexing content across all sites
Each site is identified by a unique type field in the index, allowing filtered searches per domain while maintaining a unified search infrastructure.
Important
Regular monitoring of Swiftype usage against subscription limits is essential. Track query counts, total documents indexed, and total domains indexed to avoid service disruptions.
Sites Using Swiftype
The unified Swiftype engine currently serves:
- NR1 Help Center - In-product help feature
- support.newrelic.com - Customer support portal
- docs.newrelic.com - Technical documentation
- developer.newrelic.com - Developer resources
- opensource.newrelic.com - Open source projects
- learn.newrelic.com - Educational content
- newrelic.com - Main marketing site
Key Considerations
Performance Metrics
- Auto-crawl frequency: Every 12 hours
- Average reindexing time: Up to 4 days
- Manual crawl limit: Once every 12 hours
- Index update time: Few minutes for manual additions
Next Steps
Continue to the following sections to learn specific management tasks: