Hi Michael -
In that case I would probably just write a little Perl script to run whatever
command(s) you wish against the Monitor port.
You don't need to use Radar - you can use anything to connect to the Monitor
port.
regards
Hugh
On 6 Dec 2012, at 09:24, Michael Hulko <mihu...@uwo.ca> wrote:
> Hugh..
>
> Thought of that, but the StatsLog records ALL statistics not just from the
> server but all the Realms; Clients; AuthBy's etc.....not that it is large in
> our case...after testing this, we are left with approx. 10 entries plus the
> header per interval cycle, however, since the log is Appended, we would need
> to write something a little more sophisticated to
> grep the values we want and to ensure the timing between the StatsLog
> interval and the SNMP call for the data is synchronized as not to cause
> problems which is why we were looking into the Monitor language to execute on
> demand and respond only with the Server level information. Unless I missed
> something in the docs
> related to the StatsLog that weeds out the additional details. We are
> contemplating just programtically removing the Statistics file after each
> call just to keep it pruned.
>
> What would be best is to be able to have RADAR write these values as they are
> monitored into a RRD type flat file/database for reading by other systems
> from a historical perspective.
>
> Thanks anyway, I thought I would just ask. Is there anything that would
> prevent us from adjusting the RADAR code to facilitate our needs by our
> developers?
>
> regards;
>
> MH :)
>
>
>
>
> On 2012-12-05, at 5:05 PM, Hugh Irvine wrote:
>
>>
>> Hello Michael -
>>
>> Why don't you just use the StatsLog clause?
>>
>> See sections 5.94 and 5.95 in the manual ("doc/ref.pdf").
>>
>> regards
>>
>> Hugh
>>
>>
>> On 6 Dec 2012, at 03:29, Michael Hulko <mihu...@uwo.ca> wrote:
>>
>>>
>>> It describes the command language from an external source point of view (
>>> if I read correctly ).. not from the Radiator server itself.
>>>
>>> What the challenge is we want to monitor the Radius servers from another
>>> source such as Nagios, Whatsup Gold etc. We were looking at Radar and as
>>> impressive as it is,
>>> it does not store the data historically, which is what our requirements
>>> are. The SNMP side of the monitoring does not give us the complete
>>> picture, as it there is no oid for
>>> the "Response Time" value that Radar <-> Monitor <-> StatsLog provides
>>> unless I am missing something. So, what we have done in the past is
>>> created a local custom SNMP variable through various means for us to
>>> monitor and collect stats from other systems. We could parse through the
>>> StatsLog, however, this requires a fair bit of logic and programming and
>>> not to mention timing.
>>>
>>> Having tested the Monitor command language running the command "STATS ." we
>>> find we can parse the values simply. In order for us to define a custom
>>> SNMP oid variable
>>> we need to be able to run this locally on the server itself.
>>>
>>> If there is a way that Radar could provide historical and / or write the
>>> values into a log file for extraction would be easier.
>>>
>>> Any other suggestions would be appreciated.
>>>
>>> Thanks for your time and input
>>>
>>> MH
>>>
>>> On 2012-12-04, at 4:19 PM, Heikki Vatiainen wrote:
>>>
>>>> On 12/04/2012 09:43 PM, Michael Hulko wrote:
>>>>
>>>>> Just wondering if there is a way to execute the Monitor command language
>>>>> local to the Radiator server?
>>>>
>>>> Does section 25 "Monitor command language" in doc/ref.pdf describe what
>>>> you are looking for?
>>>>
>>>> --
>>>> Heikki Vatiainen <h...@open.com.au>
>>>>
>>>> Radiator: the most portable, flexible and configurable RADIUS server
>>>> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
>>>> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
>>>> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
>>>> DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
>>>> NetWare etc.
>>>> _______________________________________________
>>>> radiator mailing list
>>>> radiator@open.com.au
>>>> http://www.open.com.au/mailman/listinfo/radiator
>>>
>>>
>>>
>>> Michael Hulko
>>> Network Analyst
>>>
>>> Western University Canada
>>> Network Operations Centre
>>> Information Technology Services
>>> 1393 Western Road, SSB 3300CC
>>> London, Ontario N6G 1G9
>>>
>>> tel: 519-661-2111 x81390
>>> e-mail: mihu...@uwo.ca <mailto:mihu...@uwo.ca>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> radiator mailing list
>>> radiator@open.com.au
>>> http://www.open.com.au/mailman/listinfo/radiator
>>
>>
>> --
>>
>> Hugh Irvine
>> h...@open.com.au
>>
>> Radiator: the most portable, flexible and configurable RADIUS server
>> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
>> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
>> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
>> DIAMETER etc.
>> Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.
>>
>
>
>
> Michael Hulko
> Network Analyst
>
> Western University Canada
> Network Operations Centre
> Information Technology Services
> 1393 Western Road, SSB 3300CC
> London, Ontario N6G 1G9
>
> tel: 519-661-2111 x81390
> e-mail: mihu...@uwo.ca <mailto:mihu...@uwo.ca>
>
>
>
>
>
--
Hugh Irvine
h...@open.com.au
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc.
Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.
_______________________________________________
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
