The future of The Dude?

RouterOS The Dude
1

Hello forum. I feel like I’m beating a thoroughly dead horse here, but I’m curious as to the future (and the current stagnant state) of The Dude.

Is it considered “good enough” and therefore will no longer be developed?
Is the development limited because it’s not a money maker, comparing to RouterOS and RouterBoard?
Are we just being impatient?

If The Dude is on the back-burner, is there any possibility of it ever becoming open-source, so the development might be taken over by the community?

The natives are getting restless :laughing:

Thanks!

2

yes - more development please!

3

eh..

4

I’ve been using Dude on and off for a couple of years.

Things I’ve learned to be constants:

  • It’s a side project for the developer, so development has been, is, and will always be slow.
  • It still has a place in the corner of MicroTik’s heart if they still develop it despite being free and despite being busy with other ventures.
  • Updates and releases happen just about the time you (as a user) feel like writing it off as dead.
  • The updates are usually worth it.
5

I am still using Dude 3.6 monitoring 1000+ devices.
Version 4 has a memory leak. It will crash after running a day or so.

6

@sup5 I would say that one or some of your probes have memory leaks, I have been running 4.3 since it became available and never have lockups. Quite a while ago someone found that memory leaks were caused by monitoring windows servers. I have not seen it but I monitor very few servers and I don’t install every probe. Anyhow if you decide to try to figure it out let us know if you do.

7

Same here, we’re running the last beta with 2k+ nodes, polling mostly with ICMP and SNMP probes. I have to restart the server process maybe once every couple of months, and occasionally clean up the history tables. Other than that, it’s quite stable.

8

I mostly do Ping probes.
rarely cpu-proces or other snmp-related stuff.
no windows-probing at all.

but I do bandwidth graphing. on most of my links. maybe this causes the version 4 dude to leak memory?

9

We maintain bandwidth graphs for close to 300 devices on our network without any problems. We do occasionally prune the really old data, just to keep the database manageable.

10

How are you purging old data? In 3.6 you can add the link to a chart and see the data in an advanced tab of some sort… In 4.3 I have found if you copy something the device or link will delete all the stored data. Kinda handy when creating new links they spike with fake bandwidth, just click copy and the data gets reset.

11

As far as trying to determine what causes the memory leak maybe delete all your charts? Or disable half the probes at a time on the services page and graph memory utilization on the server…