Jump to content
Bill.Stack

SNMP for LabTech - FINALLY PRTG has arrived

Recommended Posts

We've seen a lot of people complaining about the limitations and reliability of SNMP in LabTech, so we finally took action.

 

The team at Stack Advisors have collaborated to bring you a PRTG LabTech Plugin!

 

We are in the early stages of BETA and would like additional feedback from the community on what features they would like to see next! There is a lot on the list and in the works, but your input is needed. The current release is available at http://prtg.labtechplugins.com

 

The plugin will connect to the PRTG server via the API. You can sync the Group/Probe to the Client/Location and enable Alarms -> Alerts and Tickets.

 

Dashboards exist on the Main, Client and Location screens.

 

Settings continue to get more granular as we develop the plugin, so be sure to update when prompted.

 

For now, all features are free as we build and focus on user requested features.

 

You can get the plugin installer directly from here: http://download.labtechplugins.com/prtg/installer.exe

 

If you don't have PRTG, just fill out the form for your free trial: https://shop.paessler.com/trial/prtg/19ada252

 

Questions? Let me know here or direct message.

Share this post


Link to post
Share on other sites

First off. Great plugin we have been waiting for this for a long time. It appears the only association you can do is via a probe. Currently we run a single PRTG probe out of the DC and have it monitor and scan all of our external customer devices. Are there any plans to support this type of environment?

 

We mostly monitor for internet connectivity. Up/down, ingress and egress bandwidth, as well as firewall CPU usage.

Share this post


Link to post
Share on other sites

The plugin is sweet and setup was a breeze. However, we have the same setup as mentioned above. We use PRTG to monitor WAN Ping so all of our clients fall under a single probe which we host ourselves. Being able to map a group to a location is exactly what we need.

Share this post


Link to post
Share on other sites

Hi Bill,

 

This looks great. I will be installing and get my PRTG expert to try it out. The maintenance mode is top notch and will stop alerts from coming when we patch and reboot and forget to pause PRTG :)

Edit : So I've managed to install the plugin and connect to my server. I see in the probe "unmapped (default) : 0" but I don't understand how to do the mapping. I RTFM (http://labtechplugins.com/labtech-plugins-faq/prtg-faq/) but don't understand the mapping process.

 

Thanks,

Thomas

Share this post


Link to post
Share on other sites

When I clicked unmapped I have nothing in the dropdown list. If I use the account to login to PRTG I have access to the probes.

Share this post


Link to post
Share on other sites

Odd - did you enter this same user into the settings for the plugin as you are using for the web interface? Also, can you provide screenshots of the prtg console and prtg plugin?

Share this post


Link to post
Share on other sites

limp1500 - pop open an issue ticket in the bug/feedback form and it will get to the right guys. You should be able to get to the API interface via browser from your desktop AND the console of your LabTech Server. The plugin will initiate the connection from your local machine, but then the LabTech server will make the subsequent connections. http://serverfqdn/api.htm?tabid=1

Share this post


Link to post
Share on other sites

@vkent39 - If I understand it correctly, you would like to be able to create a group in PRTG, move items to that group and then map that group directly to the Client|Location to associate the alerts. (Or that is how you already have it set up and just want to map it).

 

It sounds like that would be a useful feature for a number of people.

 

Would mapping on a per device basis be useful?

Share this post


Link to post
Share on other sites

@Bill.Stack I think mapping on a per device level would be extremely useful for us. Also a script to install and push a PRTG probe to a client machine would be great as well. I would think it would be nice to A. have the remote probe still monitor all WAN connections and B. install a local probe to monitor all LAN connections. Having the remote probe is important to us to help identify WAN failures.

Share this post


Link to post
Share on other sites

With how the plugin is currently structured doing it based on group would be far more beneficial IMO. As it stands, we are presented with a list of clients and given the option to only select one object to associate with the client. If the structure will be kept this way, then doing it based on Group would allow multiple devices (objects) to be associated with a client because you could throw any collection of devices (objects) into a group. If it is done per device, then you will only be able to associate one object with one client.

 

If the structure changes and you are presented with a list of devices (rather than clients/locations) and you could associate a location to multiple devices. Then based on device would probably work out better.

 

Let me know if I'm craz.

Share this post


Link to post
Share on other sites

Not at all. I tend to think the right way is to give the option and include the ability to do a many-to-one mapping so that a client/location can have probes, groups or devices. The trick is to get the most common settings by default so it is quick to setup but has an advanced component that will allow you to drill in for details.

 

It seems like a map by group option would give the largest common usage, with an option to map devices individually. For an MSP that has a probe per site (what we thought was the most common usage) would simply need to assign a group name to that probe and map it.

 

Good stuff. Keep it coming.

Share this post


Link to post
Share on other sites
Not at all. I tend to think the right way is to give the option and include the ability to do a many-to-one mapping so that a client/location can have probes, groups or devices. The trick is to get the most common settings by default so it is quick to setup but has an advanced component that will allow you to drill in for details.

 

It seems like a map by group option would give the largest common usage, with an option to map devices individually. For an MSP that has a probe per site (what we thought was the most common usage) would simply need to assign a group name to that probe and map it.

 

Good stuff. Keep it coming.

 

You explained it much better than I did haha. That is definitely what I'm looking for. The ability to pause, check and add sensors would be pretty sweet as well. But I think for a v1 implementation the many-to-one mapping would be awesome.

Share this post


Link to post
Share on other sites

The next update (scheduled for Monday) will include sensor groups and sensor pausing. The plugin should notify you of an update after it is released.

Share this post


Link to post
Share on other sites

We were working on advanced device mapping between LT and PRTG, but will push that to a future release. There should be an update out later today.

Share this post


Link to post
Share on other sites

Published. Plugin should notify you.

 

- added probe management to client, allowing for pause / resume of probes and sensors for all locations

- added time frame selection on graphs tab

- added quick access to log files

- removed automatic ticket creation on loading of settings tab

- performance improvements

- UI improvements

- bug fixes

Share this post


Link to post
Share on other sites
Published. Plugin should notify you.

 

- added probe management to client, allowing for pause / resume of probes and sensors for all locations

- added time frame selection on graphs tab

- added quick access to log files

- removed automatic ticket creation on loading of settings tab

- performance improvements

- UI improvements

- bug fixes

 

How does the plugin Notify? Do we need to close Control Center and re-open or will it pop-up a notification when opening the dashboard?

Share this post


Link to post
Share on other sites

It will check once a day and notify you via the prtg plugin when you load the dashboard. You don't have to close and reopen the full CC. As we transition to a more regular update schedule, this will be a smoother process.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×