I can't help you with debugging this KM. But if you're looking for an alternative to the PATROL for Scripting KM, you have Monitoring Studio KM (Monitoring Studio X) which has been around for much longer than PATROL for Scripting KM. It has a separate license but it brings much more features.
Running commands and scripts in Monitoring Studio X: Monitoring Studio X - Monitors with Content
Extracting content: Monitoring Studio X - Content Parsing Monitors
Edits: added links
While this does not seems to be a major issue, can you share the output of the 1-liner as it's printed on command line?
Also, you can run the Script output validation utility that will 1st parse the output to confirm it's following the write format,
and if so will also present to you how this will be instantiated on TSOM UI.
I am pretty much using the same script filesystem one-liner as the one in the Patrol for Scripting video PATROL for Scripting|How to write scripts: Part 2 - YouTube
The output is as follows:
When I run it through the verification action, it shows:
TRO9021E: Reviewed text: [ACP_FS=,UsagePct=27]
Problem: Script output metadata (monitor type name and parameter name) is invalid
- Monitor type name or parameter name contains one of the following invalid characters:
If used (as is) then it will not be created in the monitoring system
After restarting the agent, the new monitortype appears in our TSIM, and /, /dev, etc, show with their correct values in the TSIM (I left it running for a day, but only started showing data after restarting our Patrol 11.3 agent).
However, the patrol agent logs show the error about the "Bad PSL Script"...
I guess the error message is about the "/" in the ACP_FS monitor type, even if it now shows in the TSIM and the script seems to be working fine.
yes, that makes sense,
patrol in general does not take SID name with /.
it's the display only which can handle this.
if at all needed we can solve that as well.
The script output that you shared with us look good, '/' character is allowed by the scripting KM.
At the first time, while the scripting KM creates the new monitor types and parameters based on your output, the PA need to be restarted, this will end with data population in TSPS OPS console.
We can have a session with the user to make sure that the scripting function as expected.