PipoCanaja
PipoCanaja
> Relational database is terrible for this kind of data. See IF-MIB stuff for details. I'm always hesitant for these types of sensors, because they are a little too generic...
> Relational database is terrible for this kind of data. See IF-MIB stuff for details. I'm always hesitant for these types of sensors, because they are a little too generic...
> @PipoCanaja Do you plan on working on this again? Hi @jerji Yes, I'll fix this PR. Moving to a new place limited drastically my spare time so I cannot...
> Just pulled this up and had a thought: Why is called count_rate and not just rate? This is a good point. No name is really covering 100% of the...
Hi @Npeca75 I would suggest to go with 2 different OSes here. Because you would end up with no PHP code at all, and only 4 YAML files. Makes the...
Hi @kamils85 Fix is on the way but I have some difficulties with the automated tests.
@kamils85 Looks like it is ready for review and hopefully merge soon. In the meantime, we'd be happy if you can test the PR and confirm it fixes your issue.
Hum, during discovery, you should not see this error anymore : ``` SQLSTATE[HY093]: Invalid parameter number (SQL: SELECT COUNT(*) from `bgpPeers` WHERE device_id = 289 AND bgpPeerIdentifier = 88.220.106.137 AND...
Ok. I'll try to reproduce the issue and come with a new PR for this one. But first I need #14278 to be merged so it won't be done with...