You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have implemented the performance Graphs in Ninja One.
The 24 hours Performance data is working well.
Yesterday (25 November) there was an alert in NINJA on drive D on a server, it was 100% full.
When I checked the 30 days performance Data to check when this happend I saw that the disk went from 23% full to 100 % full in a couple of hours.
The date shown in the graph when I hover over with my mouse was 17 november, I already find that strange because there was no alert on 17 november.
I then check the activity log in Ninja for the server to see when the first alert was triggered (there is a rule that gives an alert when the disk is 90% full and anther rule that will trigger an alert at 95%) the first alert was triggered on 22 November, not 17 november like I saw in the 30 day performance graph.
Today on 26 november when I continue to check on this problem, I see that the 30 day performance graph is giving me another date on the D drive spike, it now shows 14 November.
How is this possible that the date is not correct on the 30 day performance graph (I am sure that it will also not be correct on the 90 days graph) and that the date seems to change every day?
Is there any way you can fix your script so that it works correctly?
This is very important for us that the data in the Performance Graphs is correct, otherwise it's useless....
The text was updated successfully, but these errors were encountered:
I hope that you can look into it.
I am a IT system engineer, but I am not good with scripts.
I can not make any changes to your script to make it work.
I let the data gathering script run every 5 minutes.
Then the script to collect the data and put it in the Custom fields runs every 30 minutes.
When I scroll throw the 24 hours graph, I see every 5 minutes.
But in the 30 days graph, the timejumps are much bigger. What happens with al these datapoints in the JSON file, are some they being deleted?
Hello,
I have implemented the performance Graphs in Ninja One.
The 24 hours Performance data is working well.
Yesterday (25 November) there was an alert in NINJA on drive D on a server, it was 100% full.
When I checked the 30 days performance Data to check when this happend I saw that the disk went from 23% full to 100 % full in a couple of hours.
The date shown in the graph when I hover over with my mouse was 17 november, I already find that strange because there was no alert on 17 november.
I then check the activity log in Ninja for the server to see when the first alert was triggered (there is a rule that gives an alert when the disk is 90% full and anther rule that will trigger an alert at 95%) the first alert was triggered on 22 November, not 17 november like I saw in the 30 day performance graph.
Today on 26 november when I continue to check on this problem, I see that the 30 day performance graph is giving me another date on the D drive spike, it now shows 14 November.
How is this possible that the date is not correct on the 30 day performance graph (I am sure that it will also not be correct on the 90 days graph) and that the date seems to change every day?
Is there any way you can fix your script so that it works correctly?
This is very important for us that the data in the Performance Graphs is correct, otherwise it's useless....
The text was updated successfully, but these errors were encountered: