https://docs.foji.io/index.php?action=history&feed=atom&title=Metric_Instant_Query_Node_in_PathwaysMetric Instant Query Node in Pathways - Revision history2026-06-22T03:26:35ZRevision history for this page on the wikiMediaWiki 1.40.1https://docs.foji.io/index.php?title=Metric_Instant_Query_Node_in_Pathways&diff=2731&oldid=prevMitchell.Hirsche: Mitchell.Hirsche moved page Documentation for the "Metric Instant Query" Node in Pathways to Metric Instant Query Node in Pathways2025-03-05T22:45:30Z<p>Mitchell.Hirsche moved page <a href="/wiki/Documentation_for_the_%22Metric_Instant_Query%22_Node_in_Pathways" class="mw-redirect" title="Documentation for the "Metric Instant Query" Node in Pathways">Documentation for the "Metric Instant Query" Node in Pathways</a> to <a href="/wiki/Metric_Instant_Query_Node_in_Pathways" title="Metric Instant Query Node in Pathways">Metric Instant Query Node in Pathways</a></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 22:45, 5 March 2025</td>
</tr>
<!-- diff cache key wiki:diff::1.12:old-2678:rev-2731 -->
</table>Mitchell.Hirschehttps://docs.foji.io/index.php?title=Metric_Instant_Query_Node_in_Pathways&diff=2678&oldid=prevMitchell.Hirsche: Metric Instant Query2025-03-05T00:44:08Z<p>Metric Instant Query</p>
<p><b>New page</b></p><div>== '''Overview''' ==<br />
The '''Metric Instant Query''' node in FojiSoft Pathways allows users to execute a metric query at a specific point in time. This node is particularly useful for retrieving real-time or historical performance metrics from monitoring systems, enabling automation based on live data.<br />
----<br />
<br />
== '''Node Properties''' ==<br />
<br />
=== '''1. Name''' ===<br />
<br />
* '''Description''': A unique identifier for the metric query operation.<br />
* '''Usage''': Assign a clear and descriptive name (e.g., "Fetch Server CPU Usage" or "Retrieve API Latency").<br />
<br />
----<br />
<br />
=== '''2. Query''' ===<br />
<br />
* '''Description''': Defines the metric query that will be executed.<br />
* '''Options for Expression Type''':<br />
*# '''JavaScript Statement''': Direct JavaScript expression for simple queries.<br />
*# '''JavaScript Function''': A function for advanced dynamic queries.<br />
*# '''Handlebars Template''': A dynamic template to inject real-time query values.<br />
* '''Example Expressions''':<br />
** '''JavaScript Statement''': "server_cpu_usage"<br />
** '''JavaScript Function''': function getQuery() { return "server_cpu_usage"; }<br />
** '''Handlebars Template''': metric_query_variable<br />
* '''Status''': '''Required''' (A valid query must be provided for execution).<br />
<br />
----<br />
<br />
=== '''3. Time''' ===<br />
<br />
* '''Description''': Specifies the exact timestamp for the metric query execution.<br />
* '''Options''': Same as '''Query Type''' (JavaScript Statement, JavaScript Function, Handlebars Template).<br />
* '''Example Expressions''':<br />
** '''JavaScript Statement''': Date.now() // Fetch metric at the current time<br />
** '''JavaScript Function''': function getQueryTime() { return Date.now() - 60000; // Fetch metric from 1 minute ago }<br />
** '''Handlebars Template''': query_time_variable<br />
<br />
----<br />
<br />
=== '''4. Variable Name''' ===<br />
<br />
* '''Description''': The name of the output variable where the retrieved metric data will be stored.<br />
* '''Status''': '''Required''' (Must be defined for further use in the workflow).<br />
* '''Usage''': Choose a meaningful variable name (e.g., <code>cpu_usage</code>, <code>api_latency</code>).<br />
<br />
----<br />
<br />
== '''How It Works''' ==<br />
<br />
# '''Define the Query''': Select a query expression to retrieve the relevant metric.<br />
# '''Specify the Time''': Choose a timestamp for when the query should be executed.<br />
# '''Store Output in a Variable''': The retrieved metric data is saved under the specified variable name.<br />
<br />
----<br />
<br />
== '''Example Use Cases''' ==<br />
<br />
=== '''1. Monitoring Server Performance''' ===<br />
<br />
* '''Query''': <code>"server_cpu_usage"</code><br />
* '''Time''': <code>Date.now()</code><br />
* '''Variable Name''': <code>cpu_data</code><br />
* '''Outcome''': Retrieves the current CPU usage of a server.<br />
<br />
=== '''2. Checking API Latency Trends''' ===<br />
<br />
* '''Query''': <code>"api_response_time"</code><br />
* '''Time''': <code>Date.now() - 60000</code> (1 minute ago)<br />
* '''Variable Name''': <code>api_latency</code><br />
* '''Outcome''': Fetches API response latency from the past minute.<br />
<br />
----<br />
<br />
== '''Best Practices''' ==<br />
<br />
* '''Use Meaningful Variable Names''': Helps with workflow clarity and debugging.<br />
* '''Leverage JavaScript Functions''': For more complex query generation and timestamp manipulation.<br />
* '''Optimize Query Execution''': Avoid excessive querying by setting appropriate time intervals.<br />
<br />
The '''Metric Instant Query''' node is essential for integrating real-time performance data into automated workflows, allowing users to build intelligent, responsive systems.<br />
[[Category:ForgeAI]]<br />
[[Category:Pathways]]</div>Mitchell.Hirsche