Invoke monitor search index
The Invoke monitor search index, typically shortened to Monitor search index, is an index of all the service calls that were made within your instance – specifically those triggered by external requests or configured events. It is used internally by the system to enforce API throttling and monetization1 if you have configured rules.
Internal system design
Under the hood, all this takes to work is a Solr core called
invoke_monitor2 linked to your instance's
core package. When a request is received by TORO Integrate, it logs the service invocation by adding
a document to the aforementioned Solr core's index. Recording data this way allows the Invoke monitor service3 to
do faster, fine-grained searches for you.
Monitor versus other search indices
Unlike custom search indices or the Tracker search index, clients are not allowed to add their own documents to the Invoke monitor search index. This is to ensure the accuracy of the residing statistical data. Disabling the index is also not allowed for the same reason4.
invoke_monitorSolr core resides in an embedded Solr instance and should be migrated to a remote Solr server instead for performance boost. ↩
Refers to the family of internal services responsible for managing the Invoke monitor search index. Also called Monitor for brevity. ↩
There is no exposed configuration to stop the Invoke monitor service from creating and indexing service call documents. However, TORO Integrate is internally capable of conditionally disabling this behavior. The Invoke monitor service is on if there are monitor rules present and (1) TORO Integrate's assigned license supports throttling and monetization or (2) the license imposes limits on the number of service invokes per minute, hour, day, week, or month. ↩