1.5.00111

juanflores3 · 2016-09-07T17:58:29.000Z

Mark8081:

MrDanne:

Read that too… But if you have just a couple of devices to monitor uptime or so, you only need 1 sensor per device or if you have a small number of devices.

I did try it and it is a lot to configure Looks good though.

Yeah I’ve been trying it and I’m not sure the free version will be suitable for us. I just added one server and one switch and let it “autodiscover”. It added a total of 36 “sensors” for the server and 82 for the switch (including one sensor per port of a 48-way switch). Even with some trimming of these sensors, if I want to monitor the same devices as I was with Spiceworks Network Monitor I’ll struggle to stay below 100 sensors. And the paid version starts at 1,200 Euros for 500 sensors. I’ll struggle to justify spending money on it.

Not sure where I’ll go now. It brings home how good the Spiceworks NM would be if it was stable!

EDIT: I restarted the SW NM services and it’s working again. The product may be imperfect but it’s doing what I need, for the right price, so let’s hope it gets some resource to support it

Yes, I am struggling to get below 100 sensors with my 40 machines, plus our 6 servers. I’ll have to try other solutions.

aarongregory2 · 2016-09-07T18:31:29.000Z

I have an alert for low disk space when clearly there is 2TB available. Alerts show 0% left. I did restart that box to check for changes. No dice.

I won’t go into details now (head cold from hell) but since 1.5.00111 there has been some weird stuff going on.

popovdmitry · 2016-09-09T07:59:43.000Z

The project is closed?

conwaywharton7098 · 2016-09-09T10:35:04.000Z

Qeraser:

I have an alert for low disk space when clearly there is 2TB available. Alerts show 0% left. I did restart that box to check for changes. No dice.

I won’t go into details now (head cold from hell) but since 1.5.00111 there has been some weird stuff going on.

I’m going to guess that it is complaining about the Recovery Partition. I’ve seen this on all my servers - I just change the alerts for that device.

aarongregory2 · 2016-09-09T11:13:02.000Z

The alerts are for both C and E (E is 2TB). C never changes in available space much and E is a SAN which changes often but not near 0.

I have been running 11 devices without many problems. The problems I did have were each known problem with each release of NM. This latest alert made me uninstall NM. Maintenance windows never worked properly which created a lot of email alerts.

I can give more details now that the head cold has left the building.

Thanks, Aaron

EDIT: 8 of the devices are VMs.

danielosterberg · 2016-09-12T05:14:18.000Z

Dmitry6058:

The project is closed?

Don’t think so, looks like the issue is a bit hard to solve.

This is what I got from SW support before:

Spiceworks Support

Howdy Daniel,

I show the Dev Team is still working on the repair, but I don’t yet show an ETA on when it will be out. Unfortunately, this specific issue has been persistent through several versions of the Network Monitor and appears to be related to the AppServer memory getting overloaded as it tries to render all of the graphics to the browser which then causes problems with the AppServer and EventProcessor services. Our Dev Team is working to streamline the rendering commands to not have them use as much memory, but there isn’t a clear fix at this exact time.

conwaywharton7098 · 2016-09-12T10:22:36.000Z

MrDanne:

Dmitry6058:

The project is closed?

Don’t think so, looks like the issue is a bit hard to solve.

This is what I got from SW support before:

Spiceworks Support

Howdy Daniel,

I show the Dev Team is still working on the repair, but I don’t yet show an ETA on when it will be out. Unfortunately, this specific issue has been persistent through several versions of the Network Monitor and appears to be related to the AppServer memory getting overloaded as it tries to render all of the graphics to the browser which then causes problems with the AppServer and EventProcessor services. Our Dev Team is working to streamline the rendering commands to not have them use as much memory, but there isn’t a clear fix at this exact time.

The last word I got was that the manpower was removed from this project and put on their new cloud tools project.

danielosterberg · 2016-09-14T06:16:32.000Z

Old-Wolf:

MrDanne:

Dmitry6058:

The project is closed?

Don’t think so, looks like the issue is a bit hard to solve.

This is what I got from SW support before:

Spiceworks Support

Howdy Daniel,

I show the Dev Team is still working on the repair, but I don’t yet show an ETA on when it will be out. Unfortunately, this specific issue has been persistent through several versions of the Network Monitor and appears to be related to the AppServer memory getting overloaded as it tries to render all of the graphics to the browser which then causes problems with the AppServer and EventProcessor services. Our Dev Team is working to streamline the rendering commands to not have them use as much memory, but there isn’t a clear fix at this exact time.

The last word I got was that the manpower was removed from this project and put on their new cloud tools project.

hm… hope that you are wrong on that

juanflores3 · 2016-09-22T13:55:16.000Z

If they can’t fix this network monitor software, how can they just move to a cloud service. If that fails, are they going to move all the manpower to a new project? If that’s the case, they are going no where.

markwitteveen · 2016-09-23T04:22:37.000Z

see topic

Network Monitor Project Status Beta

After the restructuring, work on the network monitor is going at a slower pace. v1.5 is still beta. All I have in terms of progress and fixes are what is contained in the release notes which you can subscribe to for updates. https://community.spiceworks.com/blogs/network-monitor-release-notes The above is the response I got when I asked what was going on with this project. This contradicts another response I got when I questioned that the Network Monitor download button says “beta” but the gra…

There is a update comming soon.

michael-adrem · 2016-09-23T10:03:36.000Z

Mark8081:

MrDanne:

Read that too… But if you have just a couple of devices to monitor uptime or so, you only need 1 sensor per device or if you have a small number of devices.

I did try it and it is a lot to configure Looks good though.

Yeah I’ve been trying it and I’m not sure the free version will be suitable for us. I just added one server and one switch and let it “autodiscover”. It added a total of 36 “sensors” for the server and 82 for the switch (including one sensor per port of a 48-way switch). Even with some trimming of these sensors, if I want to monitor the same devices as I was with Spiceworks Network Monitor I’ll struggle to stay below 100 sensors. And the paid version starts at 1,200 Euros for 500 sensors. I’ll struggle to justify spending money on it.

Not sure where I’ll go now. It brings home how good the Spiceworks NM would be if it was stable!

EDIT: I restarted the SW NM services and it’s working again. The product may be imperfect but it’s doing what I need, for the right price, so let’s hope it gets some resource to support it

Our NetCrunch network monitoring suite is monitored by number of monitored nodes, with no limits on sensors/elements/etc on each device. A 48-port switch is one node, period.

9.2dash.PNG800×482 174 KB

danielosterberg · 2016-09-26T09:25:09.000Z

Michael (AdRem):

Mark8081:

MrDanne:

Read that too… But if you have just a couple of devices to monitor uptime or so, you only need 1 sensor per device or if you have a small number of devices.

I did try it and it is a lot to configure Looks good though.

Yeah I’ve been trying it and I’m not sure the free version will be suitable for us. I just added one server and one switch and let it “autodiscover”. It added a total of 36 “sensors” for the server and 82 for the switch (including one sensor per port of a 48-way switch). Even with some trimming of these sensors, if I want to monitor the same devices as I was with Spiceworks Network Monitor I’ll struggle to stay below 100 sensors. And the paid version starts at 1,200 Euros for 500 sensors. I’ll struggle to justify spending money on it.

Not sure where I’ll go now. It brings home how good the Spiceworks NM would be if it was stable!

EDIT: I restarted the SW NM services and it’s working again. The product may be imperfect but it’s doing what I need, for the right price, so let’s hope it gets some resource to support it

Our NetCrunch network monitoring suite is monitored by number of monitored nodes, with no limits on sensors/elements/etc on each device. A 48-port switch is one node, period.

We have Netcrunch running here too, but to get a fast and customized view, Spiceworks Network monitor is one of a kind. You look for half a second and you’ll see if something is wrong. Netcrunch is soooo messy.

techubus · 2016-09-28T16:42:19.000Z

Just adding my voice to the chorus of frustrated users. I’ve had to give up and uninstall for now. Really hoping the next update gets things back to a usable state. This was a very useful and easy to use tool that I relied upon up until the 1.5x release.

stevewong · 2016-10-06T01:13:15.000Z

Regarding: “Cannot connect to event service” error message in 1.5.00111

This error gone away after I installed all the latest Windows Updates on a Windows 2012 R2 Server. Hope this helps.

stevewong · 2016-10-06T01:27:04.000Z

Apologize for a silly newbie question …

Have a Dell PowerEdge R720 with 8 drives. Disk1 is flashing green/amber/off => predicted drive failure, yet no alert from SW NM v1.5.00111? Does NM alert only when drive is in failed state? I try googling and there are references to Spiceworks Monitors and Email Alerts. Is this a different tool from NM?

Thank you in advance.

danielosterberg · 2016-10-06T04:05:42.000Z

stevewong:

Apologize for a silly newbie question …

Have a Dell PowerEdge R720 with 8 drives. Disk1 is flashing green/amber/off => predicted drive failure, yet no alert from SW NM v1.5.00111? Does NM alert only when drive is in failed state? I try googling and there are references to Spiceworks Monitors and Email Alerts. Is this a different tool from NM?

Thank you in advance.

I don’t think it pulls that info from the server.

markpimperton · 2016-10-06T06:02:41.000Z

stevewong:

Apologize for a silly newbie question …

Have a Dell PowerEdge R720 with 8 drives. Disk1 is flashing green/amber/off => predicted drive failure, yet no alert from SW NM v1.5.00111? Does NM alert only when drive is in failed state? I try googling and there are references to Spiceworks Monitors and Email Alerts. Is this a different tool from NM?

Thank you in advance.

I think you could only get alerted to that if it wrote to the Windows Event Log and then you’d set up an alert in the “normal” Spiceworks Inventory app, not Network Monitor.

danielosterberg · 2016-10-21T11:11:01.000Z

I got Network Monitor 1.4.00264 from SW support and it works flawless. 1.5 did really f*ck up my monitoring.

robertj · 2016-10-21T18:29:14.000Z

So they should just make the 1.4 version available with a brief explanation until they have resources to move forward and fix the 1.5 stuff. I that would make everyone reasonably happy.

conwaywharton7098 · 2016-10-21T18:41:18.000Z

Actually, I’m currently using the version that you can find on page 2 of this link: https://community.spiceworks.com/topic/1788436-network-monitor-project-status?page=1#entry-6225773

So far, I have been very happy with it.