- App Search Guide: other versions:
- Installation
- Getting started
- Authentication
- Limits
- Users and access
- Guides
- Adaptive relevance events logs reference
- Analytics Tags
- Crawl web content
- Crawl a private network using a web crawler on Elastic Cloud
- Crawl custom fields using proxy
- Curations
- Elasticsearch search
- Elasticsearch index engines
- Create Elasticsearch index engines
- Configure dynamic field mappings and analyzers in an Elasticsearch index engine
- Elasticsearch engines text field conventions
- Facets
- Hierarchical Facets
- Indexing Documents
- Language Optimization
- Log settings
- Meta Engines
- Precision tuning (beta)
- Query Suggestions
- Search UI
- Relevance Tuning
- Result Settings
- Result Suggestions
- Role based access control (RBAC)
- Sanitization, Raw or Snippet
- Search
- Synonyms
- View web crawler events logs
- App Search web crawler
- Web crawler FAQ
- Web crawler reference
- Web crawler events logs reference
- API Reference
- Adaptive relevance API reference (beta)
- Analytics APIs
- Analytics clicks API
- Analytics counts API
- Analytics queries API
- API logs API
- Click API
- Credentials API
- Curations API reference
- Documents API
- Elasticsearch search API
- Engines API
- Log settings API
- Multi search API
- Query suggestion API
- Schema API
- Search API
- Search API boosts
- Search API facets
- Search API filters
- Search API group
- Search API precision (beta)
- Search API result fields
- Search API search fields
- Search API sort
- Search API analytics tags
- Search settings API
- Search Explain API
- Source engines API
- Synonyms API
- Web crawler API reference
- API Clients
- Configuration
- Known issues
- Troubleshooting
ℹ️ For new users, we recommend using our native Elasticsearch tools, rather than the standalone App Search product. We are actively developing new features and capabilities in the Elastic Stack to help you build powerful search applications.
Refer to this blog for more information.
Adaptive relevance events logs reference
editAdaptive relevance events logs reference
editThe Enterprise Search adaptive relevance logs events for curation suggestion changes.
These events register changes in adaptive relevance suggestions. Every time a suggestion is created, updated or deleted, a new event will be emitted.
Enterprise Search records these events using Elastic Common Schema (ECS), including a custom field set called appsearch.adaptive_relevance.*
for adaptive relevance specific data.
To view these events, see View adaptive relevance events logs.
This document provides a reference to these events and their fields:
Base fields
edit-
@timestamp
- A UTC timestamp of the event.
-
event.id
- A unique identifier of the event.
-
event.action
-
The action that originates the event.
All events are of type
curation_suggestion
. -
event.type
-
Contains the type of event. Can be one of:
-
creation
: A new suggestion has been proposed. -
change
: A suggestion has been updated or changed status. -
deletion
: A suggestion has been deleted.
-
-
message
- A textual description of the event (useful for displaying in a UI for human consumption).
Service fields
edit-
service.ephemeral_id
- A unique identifier of the process that generated the suggestion changes.
-
service.type
-
All events will have this set to
adaptive_relevance
. -
service.version
- Current version of the Enterprise Search product.
Process fields
edit-
process.pid
- The PID of the App Search instance.
-
process.thread.id
- The id of the thread logging the event.
Host fields
edit-
host.name
- The host name where the App Search instance is deployed.
Adaptive relevance history fields
edit-
appsearch.adaptive_relevance.engine
- Engine for the adaptive relevance curation suggestion.
-
appsearch.adaptive_relevance.query
- Query for the curation suggestion.
-
appsearch.adaptive_relevance.suggestion.curation.curation_id
- Curation identifier affected by the action.
-
appsearch.adaptive_relevance.suggestion.previous_status
- Identifies the previous status for the suggestion when the suggestion has changed status. This field is not present when the suggestion has been created for the first time.
-
appsearch.adaptive_relevance.suggestion.new_status
-
Identifies the new status for the suggestion when the suggestion has changed status.
Use this field along with
appsearch.adaptive_relevance.suggestion.previous_status
to understand the status transition for the suggestion. -
appsearch.adaptive_relevance.suggestion.curation.promoted_docs
- Contains the array of document identifiers that are promoted by the suggestion.
Was this helpful?
Thank you for your feedback.