You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// When querying for currentMetrics, we narrow down the result to only include metrics for the current service being used.
199
207
// This way, when we go to compare parsedArray to currentMetricNames, the length of the arrays should match up unless there are new metrics available to view
console.log('currentMetricNames is: ',Object.keys(currentMetricNames).length)
209
212
// Use setInterval to send queries to metrics server and then pipe responses to database
210
213
setInterval(()=>{
211
214
metricsQuery(config)
212
215
// This updates the Metrics Model with all chosen metrics. If there are no chosen metrics it sets all available metrics as chosen metrics within the metrics model.
213
216
.then(async(parsedArray)=>{
214
217
// This conditional would be used if new metrics are available to be tracked.
215
218
if(l!==parsedArray.length){
216
-
console.log('currentMetricNames is less than parsedArray length, new metrics available to track');
217
-
console.log('currentMetricNames has a length of: ',l,' and parsedArray.length is: ',parsedArray.length);
// This middleware could be used if the user would like to update their chronos data, but they would have to expose a URL/port to be queried for the Electron front end.
263
+
// This middleware could be used if the user would like to update their chronos data in real time (immediately after updating saved metrics on the Chronos desktop app), but they would have to expose a URL/port to be queried for the Electron front end.
0 commit comments