I guess that is what I like about the function probe. The graphs for the device are all organized under device / history. I'll use charts for now. Thanks for your help.
On Tue, Feb 23, 2016 at 4:21 AM, Adam Moffett <[email protected]> wrote: > If you want a graph, then you don't want to make a probe. You create > probes to check for the up/down status of something so that you can get an > alert about it. > > Look under charts, add the value you're trying to get as a data source, > and add the data source to the chart. > > > On 2/23/2016 1:16 AM, Jason McKemie wrote: > > How do you set up the SNMP probe? When I set up the type as "SNMP" I can > only seem to get it to graph the response time of the SNMP query and not > the data itself. > > On Mon, Feb 22, 2016 at 3:23 AM, Adam Moffett <[email protected]> wrote: > >> 4.0b3 >> >> I also am not using a "function" probe type anywhere. I do use the SNMP >> probe type extensively. >> >> >> On 2/22/2016 1:52 AM, Jason McKemie wrote: >> >> Upon searching in the Mikrotik Forums, it looks like this could be an >> issue with custom OIDs on the newer versions of the dude. What version are >> you using? >> >> On Sat, Feb 20, 2016 at 8:29 PM, Adam Moffett < <[email protected]> >> [email protected]> wrote: >> >>> Try >>> oid_raw("1.3.6.1.4.1.32050.2.1.27.5.0") >>> >>> I'm not totally sure what the difference is, other than sometimes that >>> one works. >>> >>> >>> >>> On 2/20/2016 8:14 PM, Jason McKemie wrote: >>> >>>> I've just started working with using the Dude for monitoring on the >>>> bench, but I'm getting a parse failed on the probe for a test device. I've >>>> attached an image showing the function and probe I created. Any ideas what >>>> I'm doing wrong? Please note that this is just a test setup using a >>>> Ubiquiti AP with no client. I'm aware that the noise floor reading is >>>> essentially useless and have no intention of graphing it in a production >>>> environment. >>>> >>>> -Jason >>>> >>> >>> >> >> > >
