Line 623 and below of includes/polling/ports.inc.php.
This should use the port's ifLastChanged if it exists, else it'll use the current polling time. At some point we decided it was totally unrealiable and decided to track it ourselves by having the database update the value when the port configuration in the database changed.
It sounds more like you'd want the "down since" number calculation changed to include the total time that the alert wasn't up (or unknown).
adam.
On 2014-04-18 22:58, Jake Turner wrote:
Thank you for your reply. I take it from your response that there is some code that will update the ifLastChange field.
Unfortunately I can not find it anywhere and as a desperate attempt to see if it were specified anywhere I performed a very dirty search: 'grep -r "ifLastChange" /etc/observium/‘ which yielded nothing of any significance.
Sorry if you feel I’m being retarded but I simply can’t find it :/
Jake Turner
On 19 Apr 2014, at 03:58, Adam Armstrong adama@memetic.org wrote:
On 2014-04-18 21:34, Jake Turner wrote:
Hmm, not sure what documentation is in the code, perhaps I was looking at the wrong files. It would appear however that the ifLastChange field is only changed whenever that particular record gets ‘updated’. The MySQL column has 'on update CURRENT_TIMESTAMP’ as it’s attribute. I’m thinking of removing that and creating a separate script to update this column with the interface change time as reported by the device.
If you're not capable of finding where it's updated in the code, you possibly don't want to be modifying the code you can't be bothered to read.
adam. _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium