NetXMS Forum

Thank You Tursiops!
Your solution is obviously logical and simple instead of my search for a roundabout way. By using simple difference value I get this:

if ($1 != 0){
    dci=FindDCIByName($node,"TotalCount");
    cur=GetDCIValue($node,dci);
    if (cur == null ) cur=0;
    PushDCIData($node,dci,cur+$1);
}
return GetDCIValue($node,$dci->id) + $1;

Hello! I'm trying to get cumulative metrics by tracking daily renewing one. So every increase of a daily metric raises an event. Then this increase must be appended to cumulative metric's meaning and ... I just can't give arguments to adding script. I checked:

1. script is working with arguments in server console and works with defined one
2. arguments are right because email action can recognize them
3. selecting Run NXSL Script give has no result in case of arguments addition to script name even if the last one does not use arguments at all. I'm very sad...
4. any walked roundabout way of script execution doesn't work
5. I haven't found a way to get current value of PushAgent characteristics from .bat command file
6. script can't get any object reference another way but arguments OR may be I'm wrong?

obj = FindObject($1); //get object
cur = GetDCIValue(obj, FindDCIByName(obj, "TotalCount")); //get current value
if (cur == null)
    cur = 0;
PushDCIData(obj, FindDCIByName(obj, "TotalCount"), cur + $2); //increase it

 
Can you suggest any way to push increase of cumulative metric, please? I have no right ideas

Thank you very much! I was inattentive :-[ Don't know why but now this serene perception of all my attempts reminds me light clouds floating across the sky ???

@filipp-sudanov said in Push DCI values due to register maintenance operations:

Try to use -P instead of -p.

For me at first it had sounded like a joke (P - parking)

Hello! I am on my way to account periodic maintenance operations - a toner change, waste a toner box, consumables (DrumUnit for example) replacement and I found that snmp in netxms could be helpful for this question too, because each modern MFP shows a lifetime counter and each component part has it's own lifetime resource too.
Fixing a counter in individual metrics script is an absurd, so I reach to acqusition of maintenance lifetime stamps through Push Agent. I get the lifetime counter through nxsnmpget and for /f "tokens=3", then...
Then I check nxpush and found that in 3.1.3 Windows version of NetXMS it does not work at all! It just shows help information and checks existence of one "-" after it. No output, no errors\events on a server!
A command like 'nxpush -u pa -p secret localhost 4352:WasteTonerClean=21333' has no result. As well as 'nxpush -USA pa -p notsecret localhostel 43fifty2->WasteTonerClean~=21333' in each combination of wrong parameters.
I've read Administrator's quide but user's on our server does not have a "Push Data" rights option. And no other barrier for the command execution! Why doesn't work? ЧЯДНТ? Please help me to realize this simple idea:)