loongsuite-go

OpenTelemetry Compile-Time Instrumentation for Golang

Runssource: GitHubhomepageGoApache-2.0commit cac400935add

Go, Apache-2.0 licensed. The project labels itself: apm, go, instrumentation, metrics, observability, opentelemetry and tracing.

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

The otel binary builds and runs; all non-Docker integration tests pass; the pkg module unit tests pass; the tool prints its version and usage correctly.

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.11 (measured)
recorded runs
2
last tested
stars
907
forks
130
open issues
31
watchers
11
size
159 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 loongsuite-go, 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.

  • Go 1.25+ not pre-installed in container; cannot build without it1 minute
  • make build requires git describe but no tags exist; fatal: No names found, cannot describe anything.
  • TestPlugins1/rabbitmq_cascading-1.10.0-test: rootless Docker not found - testcontainers cannot launch RabbitMQ container
Install time
3 minutes
Cold machine to finish
36 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
go test -short -timeout 30m github.com/alibaba/loongsuite-go/test: 15 core tests passed (TestBuildProject through TestRunHttpclient), 1 Docker-dependent test skipped (rabbitmq_cascading); cd pkg && go test ./inst-api/... ./inst-api-semconv/... ./sdkconfig/... ./testaccess/...: all units passed; ./otel version returned 'otel version _cac4009'; ./otel printed usage correctly
Model tokens used
244,627
Exact commit tested
cac400935add
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.

Build: make build completed
Tests: go test -short core passed, pkg unit tests passed
Docker test skipped: no Docker in container
exec
/bin/sh -lc "ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"install_mi…
 exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:: not found
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
 succeeded in 0ms:
tokens used
244,627

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.
  • Installed in 3 minutes, faster than the median of the 4 comparable projects Argusic has measured.
  • 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 5 apm projects Argusic has installed and timed, loongsuite-go was the 1st fastest to reach a running state, and 4 of 5 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.
  • A quick evaluation: it was running 3 minutes after the clone.

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 Runner2/3Runs100.000.11
Argusic Runner1/3Runs100.000.16

Topics (from GitHub)

apmgoinstrumentationmetricsobservabilityopentelemetrytracing

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/loongsuite-go.svg)](https://argusic.com/subject/loongsuite-go)

Questions

Does loongsuite-go run?
Yes. loongsuite-go runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test loongsuite-go?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit cac400935add. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test loongsuite-go?
The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does loongsuite-go take to install?
3 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 loongsuite-go need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing loongsuite-go?
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 loongsuite-go compare with the alternatives?
Of the 5 apm projects Argusic has installed and timed, loongsuite-go was the 1st fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for loongsuite-go?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion