FortiMonitor: Outdated? Bugs?

[Secucard]

Hi,

I play around with Fortimonitor on the Cloud trial. And to be honest, it seems to have potential.

It has  the possibility for a quick and dirty integration.

BUT we also found a lot of bugs, but can not report them, because, of missing contract. And no, we do not buy, before the bugs are fixed.

However; it seems, nobody really seems to use this kind of monitoring-tool. This is the only explanation why so many bugs seems to be there, or even many things do not work or documentation is outdated.

- Mongodb. Seems to work on Replicasets only up to V6, with V7, it does not recognize the replica-status, because of new json output format, also, it still searches for mongo - binary, which is now mongosh ...

- Rabbitmq completely fails because of hard python code error

Who from Fortinet could debug this with me, that we could solve this issues? I am volent to debug it with you and help. But somebody has to take care on it from your site.

Best

Ronny

[Stephen_G]

Hello,

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

If anyone viewing this topic has any knowledge on this, I encourage you to reply.

Thanks,

[Secucard]

@Stephen_G 

Beginning with mongodb v7 I think, mongosh was introduced and mongo binary was removed. So, your code does not work anymore. What a pitty.

In the old output, it was *Javascript*, and the new mongosh, supports JSON directly.

You need:

- add import json in the header to import native json support

- the function custom_json_converter can be removed completly, there is no need to handle datetime formats (in the past, you needed it to replace ISODate and so on)

- change path to the mongo-agent to mongosh

- query should be formatted to JSON directly and then loaded into a dict

- strip and re.sub is not needed anymore, because, we already have a JSON directly

- extra function call / try to cleaned JSON to dict is not nessesary then

[Secucard]

I would really upload a file here with fixed code, but I am not sure if this violates copy rights, so I send the diff to @Stephen_G and I can also send a fixed mongo.py if you want, but is not possible here, please send me a PM with your mail and I can provide the file which can then be inserted into KB or new release.

However, we are stuck with Fortimonitor. Sorry. So many problems and bugs,

also, Support is unfriendly and not able to help without a support contract.

I am not able to buy a buggy product, debug it on my very own, and then pay for something to receive a bugfix implementated in the product *YOU* sell.

[Secucard]

Here ist the diff