ApplicationInsights-JS

Microsoft Application Insights SDK for JavaScript

Runssource: GitHubTypeScriptMITcommit 10aa1209697f

TypeScript, MIT licensed. The project labels itself: analytics, application insights, azure, javascript, monitoring, observability, pageviews and sdk.

ApplicationInsights-JS runs. An Argusic agent installed it in 52 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Rush install, full build (all 31 packages), and all 18 test suites (thousands of tests in headless Chrome) passed with zero failures.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.16 (measured)
recorded runs
1
last tested
stars
686
forks
264
open issues
59
watchers
112
size
40 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing ApplicationInsights-JS, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • tools/pureAnnotations.mjs: ESM import { parse } from "acorn" fails in Rush+pnpm+Node 18 setup because acorn's exports array is not resolved correctly10 minutes
  • Puppeteer test failure: Could not find Chrome (headless browser not installed)5 minutes
  • TypeScript compilation error: Cannot find module @nevware21/ts-async in analytics-js tests5 minutes
Install time
52 minutes
Cold machine to finish
58 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
rush test exited 0: 18 test operations succeeded, 0 failed, 0 blocked. Individual test suites reported 0 failures (e.g. 972 tests in core, 125 in dependencies, 94 in analytics, 75 in clickanalytics, 60 in AISKU). pureAnnotations.test.mjs also passed.
Model tokens used
1,350,393
Exact commit tested
10aa1209697f
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

All test operations succeeded: 18 SUCCESS, 0 FAILURE
Now let me record the final ARGUSIC_RESULT.
exec
/bin/sh -lc 'cd /work/repo && node common/scripts/install-run-rush.js test 2>&1 | grep -E "''^>> [0…
I have all the data needed from the earlier successful run. Let me compile the final report
exec
/bin/sh -lc 'kill -9 $(ps aux | grep "[r]ush" | awk '"'{print "'$2}'"') 2>/dev/null; echo \"done\""…
 succeeded in 0ms:
done
 exited 137 in 344106ms:
tokens used
1,350,393

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Took 52 minutes to install, slower than the median of the 18 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 19 analytics projects Argusic has installed and timed, ApplicationInsights-JS was the 19th fastest to reach a running state, and 15 of 19 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.16

Topics (from GitHub)

analyticsapplication-insightsazurejavascriptmonitoringobservabilitypageviewssdktypescriptusage

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/ApplicationInsights-JS.svg)](https://argusic.com/subject/applicationinsights-js)

Questions

Does ApplicationInsights-JS run?
Yes. ApplicationInsights-JS runs. Argusic installed and launched it on a clean machine in 52 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test ApplicationInsights-JS?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 10aa1209697f. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ApplicationInsights-JS?
The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ApplicationInsights-JS take to install?
52 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does ApplicationInsights-JS need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ApplicationInsights-JS?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does ApplicationInsights-JS compare with the alternatives?
Of the 19 analytics projects Argusic has installed and timed, ApplicationInsights-JS was the 19th fastest to reach a running state, and 15 of 19 reached one at all.
Where is the evidence for ApplicationInsights-JS?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion