TPS is not being monitored on Fabric

[M0dEx]

Bug Report

System Information

• AMP installation: AMP Docker image on unRAID 6.11.5
• AMP version: v20230316.1, built 16/03/2023 03:00
• AMP release channel: Nightly
• Minecraft server type and version: Fabric 0.14.17, Minecraft 1.18.2

I confirm:

• [X] that I have searched for an existing bug report for this issue.
• [X] that I am using the latest available version of AMP.

• [X] that my operating system is up-to-date.

Symptoms

What are you trying to do?

• Enable TPS monitoring for a Fabric server
• Spark is installed and active

  What are you expecting to happen?

• TPS monitoring should become active and should be displayed on the status page

  What is actually happening?

• The TPS monitoring does not become active, even after AMP successfully executes the command spark tps:

Reproduction

1. Install AMP using the Docker image mentioned above
2. Setup a Minecraft instance using Fabric
3. Install Spark for TPS monitoring
4. Enable TPS monitoring in Configuration -> Server Settings
5. Start the server and wait for it to complete
6. See spark tps being executed exactly once and TPS monitoring not activating

[PhonicUK]

AMP doesn't recognise the syntax being used for the output, the fact that it's over multiple lines makes this difficult to handle - but I'll see if I can do anything.

Also, please paste logs as text - not as screenshots. Otherwise I can't copy/paste/search.

[M0dEx]

AMP doesn't recognise the syntax being used for the output, the fact that it's over multiple lines makes this difficult to handle - but I'll see if I can do anything.

This is what /tick rate from the Carpet mod looks like (which seems much easier to parse): The tick rate is unfortunately broadcasted in chat, so I guess that takes Carpet out of the equation.

Current tps is: 20.0

However, keep in mind that Carpet is a lot less popular than Spark (1.5m downloads vs 37m downloads on CurseForge).

Also, please paste logs as text - not as screenshots. Otherwise I can't copy/paste/search.

Sorry for that, here is the spark tps output as text:

[⚡]: TPS from last 5s, 10s, 1m, 5m, 15m:
[⚡]: *20.0, 20.0, *20.0, *20.0, *20.0
[⚡]
[⚡]: Tick durations (min/med/95%ile/max ms) from last 10s, 1m:
[⚡]: 0.2/0.2/0.2/3.2; 0.2/0.2/0.3/3.2
[⚡]
[⚡]: CPU usage from last 10s, 1m, 15m:
[⚡]: 2%, 2%, 9% (system)
[⚡]: 0%, 0%, 7% (process)