本站用于记录日常工作内容,虚拟化云计算,数据库DBA,网络与安全。
 
0
之前安装好 zabbix3.2与oracle,具体详见:http://www.92cto.com/blog/1953.html需要添加服务器的应用服务的日志监控与系统登陆信息监控,这里就作一个简单的例子。在zabbix上配置监控主机后,添加监控项目:监控日志key首先要了解key,log[ file  ,<regexp>,<encoding>,<maxlines>,<mode>,<output>]file:文件名,写绝对路径regexp:要匹配内容的正则表达式,或者直接写你要检索的内容也可以,例如我想检索带ERROR关键词的记录encoding:编码相关,留空即可maxlines:一次性最多提交多少行,这个参数覆盖配置文件zabbxi_agentd.conf中的’MaxLinesPerSecond’,我们也可以留空mode:默认是all,也可以是skip,skip会跳过老数据output:输出给zabbix server的数据。可以是\1、\2一直\9,\1表示第一个正则表达式匹配出得内容,\2表示第二个正则表达式匹配错的内容。项目:oracle_error_log类型 : zabbix agent(active)键值   :  log[/data/app/oracle/diag/rdbms/hextrack/hextrack/trace/alert_hextrack.log,"Warning|ORA\-",gbk,,,]这里是监控oracle告警文件中Warning或是ORA-开头的内容,采用GBK编码。信...
Centos6 源码编译安装zabbix3.2,对接oralce11g数据库Centos6 源码编译安装zabbix3.2,对接oralce11g数据库由于mysql用时间长了,性能会下降,所以需要对接oracle数据库。具体环境如下:30台服务器主机:RHEL6+JDK1.7+java程序。4台服务器主机: RHEL6+JDK1.7+weblogic10.32台主机安装数据库: RHEL6+oracle 11gr2.0.4+ISCSI存储。1台监控主机环境:RHEL6+Zabbix3.2之前安装好了oracle11gr2.0.4,不过使用的是GBK编码,但是zabbix是要求UTF-8的编码,这里我也不修改数据编码了。生产环境中,oracle还是要用UTF8编码,不然会有乱码的。添加好单独的表空间,再配置zabbix所需oracle账号信息:-- Create the user create user ZABBIX IDENTIFIED BY zabbix ACCOUNT UNLOCK;  default tablespace ZABBIX  temporary tablespace TEMP  profile DEFAULT  password expire;-- Grant/Revoke role privileges grant connect to ZABBIX;grant resource to ZABBIX;GRANT CREATE ANY DIRECTORY TO ZABBIX;GRANT DROP ANY DIRECTORY TO ZABBIX;-- Grant/Revoke system privileges grant drop any directory to ZABBIX;grant unlimited tablespace to ZABBIX;修改需要导入...
Log file monitoringOverviewZabbix can be used for centralized monitoring and analysis of log files with/without log rotation support. Notifications can be used to warn users when a log file contains certain strings or string patterns.To monitor a log file you must have: Zabbix agent running on the host log monitoring item set upThe size limit of a monitored log file depends on large file support.ConfigurationVerify agent parametersMake sure that in the agent configuration file: 'Hostname' parameter matches the host name in the frontend Servers in the 'ServerActive' parameter are specified for the processing of active checksItem configurationConfigure a log monitoring item: Specifically for log monitoring items you enter:TypeSelect Zabbix agent (active) here.KeySet either:log[/path/to/file/file_name,<regexp>,<encoding>,<maxlines>,<mode>,<output>,<maxdelay>]orlogrt[/path/to/file/regexp_describing_filename_pattern,<regexp>,<encoding>,<ma...
 
0

zabbix agent protocol说明

发表者:admin分类:监控安全2017-03-21 17:30:21 阅读[21]
zabbix agent/3.0Contents1 Zabbix agent protocol1.1 Active agents1.1.1 Items to be monitored exist1.1.2 No active items1.1.3 Host does not exist1.1.4 Host not monitored1.1.5 Meta information updateZabbix agent protocolActive agents Note: Also see the description in the zabbix manualWhen an active agent starts, it connects to the server to ask for any item it should be monitoring:{ "request":"active checks", "host":"Host name" } If host has metadata to send, it is included in this request:{ "host": "Host name", "host_metadata": "apache|mysql|postfix", "request": "active checks" } If host has non-default listen IP or port set, they are included in this request:{ "host": "Host name", "ip": "127.0.0.1", "port": 10055, "request": "active checks" } Items ...
tag@cwtdb2 ~]$ free -g-bash: fork: Cannot allocate memoryThere is also /proc/sys/kernel/pid_max file, which specifies the value at which PIDs wrap around (i.e., the value in this file is one greater than the maximum PID). The default value for this file, 32768, results in the same range of PIDs as on earlier kernels (<=2.4). The value in this file can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 million). Increasing the value will help on large Linux system or clusters to ease process identification and process management. You can easily prevent fork() failures error message with this hack. Display Current Process Identifiers Limit On a Linux Based SystemsType the following command at shell prompt: $ sysctl kernel.pid_max OR $ cat /proc/sys/kernel/pid_max OR $ sysctl kernel.pid_max Sample outputs:kernel.pid_max = 32768Allow for more PIDs on a Linux based systemsup to 222 = 4,194,304Type the following command: # sysctl -w kernel.pid_max=4194303 OR # echo 4194303 ...
Oracle在10g中引入了闪回区(flash recovery area)的概念,用以简化和完善备份,但是闪回区同样需要精心规划和设置,否则一样会遇到问题,从Oracle10gR2开始,Oracle还提供了一个新的视图V$FLASH_RECOVERY_AREA_USAGE,用以监控闪回区空间的耗用情况。本文简要介绍Oracle闪回区的警报和空间维护机制。每次RMAN在闪回区(flash recovery area)创建文件时,会同时更新可删除文件列表。当闪回区存在空间压力时,Oracle会自动从闪回区中删除废弃文件,当没有更多空间可以释放时,Oracle会给出空间压力警报。当空间使用达到100%,数据库将会因为无法归档等原因挂起。闪回区的大小由:db_recovery_file_dest_size 参数指定。路径由: db_recovery_file_dest 参赛指定。 SQL> show parameter db_recovery NAME                                 TYPE        VALUE ------------------------------------ ----------- ----------------------------...
    总共311页,当前第1页 | 页数:
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7