Re: Monitoring Oracle ASM space....nagios? Other options?
- From: Mikhail Velikikh <mvelikikh@xxxxxxxxx>
- To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 5 Dec 2016 13:58:31 +0700
2016-12-02 14:54 GMT+07:00 Mladen Gogala <gogala.mladen@xxxxxxxxx>:
Hi Mark,
The last time I was working with Nagios (2011), it was able to execute
Perl scripts as plugins. The query that needs to be executed by the Perl
script is
select name,total_mb,free_mb,free_mb/total_mb as "FREE%" from v$asm_diskgroup
order by 3;
The problem groups will be shown first. The plugin that I was using was
this:
https://exchange.nagios.org/directory/Databases/Plugins/
Oracle/check_sql_query/details
However, half a decade has gone by, my hair is getting thinner and the
details about the configuration have been long forgotten. You will probably
have to suffer until you configure it correctly, but the pain will be
considerably less than with OEM
Hello,
I would rather use v$asm_diskgroup_stat and other %_STAT counterparts to
query an ASM instance in such kind of monitoring.
Apart from the fact that these views are more lightweight (see, for
example:
https://docs.oracle.com/database/121/REFRN/GUID-04A4009D-3B89-4C7A-B39A-FF313FB720DB.htm#REFRN30361
V$ASM_DISKGROUP_STAT displays performance statistics in the same way that
V$ASM_DISKGROUP does, but without performing discovery of new disk groups.
This results in a less expensive operation)
,
they do not lead to additional trace file generation (for instance: An ASM
Rebalance Trace File Constantly Growing While No Rebalance Is Running In
ASM (Doc ID 1582990.1)).
I have just queried v$asm_diskgroup from a RAC database using the proposed
query and I got a new trace file in the ASM instance ADR home containing
these lines:
*** ACTION NAME:() 2016-12-05 06:51:12.237
Initialized kgfd context:0x7feb657d8188
Terminating kgfd context 0x7feb657d8188
*** 2016-12-05 06:51:23.302
Initialized kgfd context:0x7feb657d7d70
*** 2016-12-05 06:51:23.369
Terminating kgfd context 0x7feb657d7d70
The same query against v$asm_diskgroup_stat does not generate any trace
data.
Other related posts: