ini Ganlia样本配置

Posted 2021-05-24

/* This configuration is as close to 2.5.x default behavior as possible
   The values closely match ./gmond/metric.h definitions in 2.5.x */
globals {
  daemonize = yes
  setuid = yes
  user = ganglia
  debug_level = 0
  max_udp_msg_len = 1472
  mute = no
  deaf = no
  allow_extra_data = yes
  host_dmax = 86400 /*secs, set this to remove dead host */
  cleanup_threshold = 300 /*secs */
  gexec = no
  send_metadata_interval = 30 /*secs, set this, or sometimes gmond will stuck */
}

/*
 * The cluster attributes specified will be used as part of the <CLUSTER>
 * tag that will wrap all hosts collected by this instance.
 */
cluster {
  name = "cluster_name_to_change"
  owner = "Allyes"
  latlong = "unspecified"
  url = "unspecified"
}

/* The host section describes attributes of the host, like the location */
host {
  location = "unspecified"
}

/* Feel free to specify as many udp_send_channels as you like.  Gmond
   used to only support having a single channel */
udp_send_channel {
  #bind_hostname = yes # Highly recommended, soon to be default.
                       # This option tells gmond to use a source address
                       # that resolves to the machine's hostname.  Without
                       # this, the metrics may appear to come from any
                       # interface and the DNS names associated with
                       # those IPs will be used to create the RRDs.
  host = host_name_to_change
  port = 8649
  ttl = 1
}

/* You can specify as many udp_recv_channels as you like as well. */
udp_recv_channel {
  port = 8649
}

/* You can specify as many tcp_accept_channels as you like to share
   an xml description of the state of the cluster */
tcp_accept_channel {
  port = 8649
}

/* Each metrics module that is referenced by gmond must be specified and
   loaded. If the module has been statically linked with gmond, it does
   not require a load path. However all dynamically loadable modules must
   include a load path. */
modules {
  module {
    name = "core_metrics"
  }
  module {
    name = "cpu_module"
    path = "modcpu.so"
  }
  module {
    name = "disk_module"
    path = "moddisk.so"
  }
  module {
    name = "load_module"
    path = "modload.so"
  }
  module {
    name = "mem_module"
    path = "modmem.so"
  }
  module {
    name = "net_module"
    path = "modnet.so"
  }
  module {
    name = "proc_module"
    path = "modproc.so"
  }
  module {
    name = "sys_module"
    path = "modsys.so"
  }
}

include ('/etc/ganglia/conf.d/*.conf')

/* The old internal 2.5.x metric array has been replaced by the following
   collection_group directives.  What follows is the default behavior for
   collecting and sending metrics that is as close to 2.5.x behavior as
   possible. */

/* This collection group will cause a heartbeat (or beacon) to be sent every
   20 seconds.  In the heartbeat is the GMOND_STARTED data which expresses
   the age of the running gmond. */
collection_group {
  collect_once = yes
  time_threshold = 20
  metric {
    name = "heartbeat"
  }
}

/* This collection group will send general info about this host every
   1200 secs.
   This information doesn't change between reboots and is only collected
   once. */
collection_group {
  collect_once = yes
  time_threshold = 1200
  metric {
    name = "cpu_num"
    title = "CPU Count"
  }
  metric {
    name = "cpu_speed"
    title = "CPU Speed"
  }
  metric {
    name = "mem_total"
    title = "Memory Total"
  }
  /* Should this be here? Swap can be added/removed between reboots. */
  metric {
    name = "swap_total"
    title = "Swap Space Total"
  }
  metric {
    name = "boottime"
    title = "Last Boot Time"
  }
  metric {
    name = "machine_type"
    title = "Machine Type"
  }
  metric {
    name = "os_name"
    title = "Operating System"
  }
  metric {
    name = "os_release"
    title = "Operating System Release"
  }
  metric {
    name = "location"
    title = "Location"
  }
}

/* This collection group will send the status of gexecd for this host
   every 300 secs.*/
/* Unlike 2.5.x the default behavior is to report gexecd OFF. */
collection_group {
  collect_once = yes
  time_threshold = 300
  metric {
    name = "gexec"
    title = "Gexec Status"
  }
}

/* This collection group will collect the CPU status info every 20 secs.
   The time threshold is set to 90 seconds.  In honesty, this
   time_threshold could be set significantly higher to reduce
   unneccessary  network chatter. */
collection_group {
  collect_every = 20
  time_threshold = 90
  /* CPU status */
  metric {
    name = "cpu_user"
    value_threshold = "1.0"
    title = "CPU User"
  }
  metric {
    name = "cpu_system"
    value_threshold = "1.0"
    title = "CPU System"
  }
  metric {
    name = "cpu_idle"
    value_threshold = "5.0"
    title = "CPU Idle"
  }
  metric {
    name = "cpu_nice"
    value_threshold = "1.0"
    title = "CPU Nice"
  }
  metric {
    name = "cpu_aidle"
    value_threshold = "5.0"
    title = "CPU aidle"
  }
  metric {
    name = "cpu_wio"
    value_threshold = "1.0"
    title = "CPU wio"
  }
  /* The next two metrics are optional if you want more detail...
     ... since they are accounted for in cpu_system.
  metric {
    name = "cpu_intr"
    value_threshold = "1.0"
    title = "CPU intr"
  }
  metric {
    name = "cpu_sintr"
    value_threshold = "1.0"
    title = "CPU sintr"
  }
  */
}

collection_group {
  collect_every = 20
  time_threshold = 90
  /* Load Averages */
  metric {
    name = "load_one"
    value_threshold = "1.0"
    title = "One Minute Load Average"
  }
  metric {
    name = "load_five"
    value_threshold = "1.0"
    title = "Five Minute Load Average"
  }
  metric {
    name = "load_fifteen"
    value_threshold = "1.0"
    title = "Fifteen Minute Load Average"
  }
}

/* This group collects the number of running and total processes */
collection_group {
  collect_every = 80
  time_threshold = 950
  metric {
    name = "proc_run"
    value_threshold = "1.0"
    title = "Total Running Processes"
  }
  metric {
    name = "proc_total"
    value_threshold = "1.0"
    title = "Total Processes"
  }
}

/* This collection group grabs the volatile memory metrics every 40 secs and
   sends them at least every 180 secs.  This time_threshold can be increased
   significantly to reduce unneeded network traffic. */
collection_group {
  collect_every = 40
  time_threshold = 180
  metric {
    name = "mem_free"
    value_threshold = "1024.0"
    title = "Free Memory"
  }
  metric {
    name = "mem_shared"
    value_threshold = "1024.0"
    title = "Shared Memory"
  }
  metric {
    name = "mem_buffers"
    value_threshold = "1024.0"
    title = "Memory Buffers"
  }
  metric {
    name = "mem_cached"
    value_threshold = "1024.0"
    title = "Cached Memory"
  }
  metric {
    name = "swap_free"
    value_threshold = "1024.0"
    title = "Free Swap Space"
  }
}

collection_group {
  collect_every = 40
  time_threshold = 300
  metric {
    name = "bytes_out"
    value_threshold = 4096
    title = "Bytes Sent"
  }
  metric {
    name = "bytes_in"
    value_threshold = 4096
    title = "Bytes Received"
  }
  metric {
    name = "pkts_in"
    value_threshold = 256
    title = "Packets Received"
  }
  metric {
    name = "pkts_out"
    value_threshold = 256
    title = "Packets Sent"
  }
}

/* Different than 2.5.x default since the old config made no sense */
collection_group {
  collect_every = 1800
  time_threshold = 3600
  metric {
    name = "disk_total"
    value_threshold = 1.0
    title = "Total Disk Space"
  }
}

collection_group {
  collect_every = 40
  time_threshold = 180
  metric {
    name = "disk_free"
    value_threshold = 1.0
    title = "Disk Space Available"
  }
  metric {
    name = "part_max_used"
    value_threshold = 1.0
    title = "Maximum Disk Space Used"
  }
}

# This is an example of a Ganglia Meta Daemon configuration file
#                http://ganglia.sourceforge.net/
#
# $Id: gmetad.conf 667 2006-07-20 08:49:41Z knobi1 $
#
#-------------------------------------------------------------------------------
# Setting the debug_level to 1 will keep daemon in the forground and
# show only error messages. Setting this value higher than 1 will make 
# gmetad output debugging information and stay in the foreground.
# default: 0
# debug_level 10
#
#-------------------------------------------------------------------------------
# What to monitor. The most important section of this file. 
#
# The data_source tag specifies either a cluster or a grid to
# monitor. If we detect the source is a cluster, we will maintain a complete
# set of RRD databases for it, which can be used to create historical 
# graphs of the metrics. If the source is a grid (it comes from another gmetad),
# we will only maintain summary RRDs for it.
#
# Format: 
# data_source "my cluster" [polling interval] address1:port addreses2:port ...
# 
# The keyword 'data_source' must immediately be followed by a unique
# string which identifies the source, then an optional polling interval in 
# seconds. The source will be polled at this interval on average. 
# If the polling interval is omitted, 15sec is asssumed. 
#
# A list of machines which service the data source follows, in the 
# format ip:port, or name:port. If a port is not specified then 8649
# (the default gmond port) is assumed.
# default: There is no default value
#
# data_source "my cluster" 10 localhost  my.machine.edu:8649  1.2.3.5:8655
# data_source "my grid" 50 1.3.4.7:8655 grid.org:8651 grid-backup.org:8651
# data_source "another source" 1.3.4.7:8655  1.3.4.8

data_source "Hadoop" dspprod-m:8649
data_source "Console" dspprod-c:8649
data_source "App" dspprod-a1:8649

gridname "Allyes Dsp Hangzhou"

# 15 seconds for 1 month, 6 minutes for 1 year
RRAs "RRA:AVERAGE:0.5:1:178560" "RRA:AVERAGE:0.5:24:88800"
rrd_rootdir "/data/ganglia/rrds"
#
# Round-Robin Archives
# You can specify custom Round-Robin archives here (defaults are listed below)
#
# RRAs "RRA:AVERAGE:0.5:1:244" "RRA:AVERAGE:0.5:24:244" "RRA:AVERAGE:0.5:168:244" "RRA:AVERAGE:0.5:672:244" \
#      "RRA:AVERAGE:0.5:5760:374"
#

#
#-------------------------------------------------------------------------------
# Scalability mode. If on, we summarize over downstream grids, and respect
# authority tags. If off, we take on 2.5.0-era behavior: we do not wrap our output
# in <GRID></GRID> tags, we ignore all <GRID> tags we see, and always assume
# we are the "authority" on data source feeds. This approach does not scale to
# large groups of clusters, but is provided for backwards compatibility.
# default: on
# scalable off
#
#-------------------------------------------------------------------------------
# The name of this Grid. All the data sources above will be wrapped in a GRID
# tag with this name.
# default: Unspecified
# gridname "MyGrid"
#
#-------------------------------------------------------------------------------
# The authority URL for this grid. Used by other gmetads to locate graphs
# for our data sources. Generally points to a ganglia/
# website on this machine.
# default: "http://hostname/ganglia/",
#   where hostname is the name of this machine, as defined by gethostname().
# authority "http://mycluster.org/newprefix/"
#
#-------------------------------------------------------------------------------
# List of machines this gmetad will share XML with. Localhost
# is always trusted. 
# default: There is no default value
# trusted_hosts 127.0.0.1 169.229.50.165 my.gmetad.org
#
#-------------------------------------------------------------------------------
# If you want any host which connects to the gmetad XML to receive
# data, then set this value to "on"
# default: off
# all_trusted on
#
#-------------------------------------------------------------------------------
# If you don't want gmetad to setuid then set this to off
# default: on
# setuid off
#
#-------------------------------------------------------------------------------
# User gmetad will setuid to (defaults to "ganglia")
# default: "ganglia"
# setuid_username "ganglia"
#
#-------------------------------------------------------------------------------
# The port gmetad will answer requests for XML
# default: 8651
# xml_port 8651
#
#-------------------------------------------------------------------------------
# The port gmetad will answer queries for XML. This facility allows
# simple subtree and summation views of the XML tree.
# default: 8652
# interactive_port 8652
#
#-------------------------------------------------------------------------------
# The number of threads answering XML requests
# default: 4
# server_threads 10
#
#-------------------------------------------------------------------------------
# Where gmetad stores its round-robin databases
# default: "/var/lib/ganglia/rrds"
# rrd_rootdir "/some/other/place"

MySQL配置文件-my.ini

原文地址：http://www.cnblogs.com/Ray-xujianguo/p/3322455.html

 

MySQL配置文件-my.ini

下面允许我介绍一下MySQL的my.ini配置文件：

my.ini是什么？

　　my.ini是MySQL数据库中使用的配置文件，修改这个文件可以达到更新配置的目的。

my.ini存放在哪里？

　　my.ini存放在MySql安装的根目录，如图所示：

　　

my.ini的具体内容介绍：

 1 # CLIENT SECTION
 2 # ----------------------------------------------------------------------
 3 #
 4 # The following options will be read by MySQL client applications.
 5 # Note that only client applications shipped by MySQL are guaranteed
 6 # to read this section. If you want your own MySQL client program to
 7 # honor these values, you need to specify it as an option during the
 8 # MySQL client library initialization.
 9 #
10 [client]
11 
12 port=3306
13 
14 [mysql]
15 
16 default-character-set=gb2312

上面显示的是客户端的参数，[client]和[mysql]都是客户端，下面是参数简介：

　　1.port参数表示的是MySQL数据库的端口，默认的端口是3306，如果你需要更改端口号的话，就可以通过在这里修改。

　　2.default-character-set参数是客户端默认的字符集，如果你希望它支持中文，可以设置成gbk或者utf8。

　　3.这里还有一个password参数，在这里设置了password参数的值就可以在登陆时不用输入密码直接进入

 

 

 1 # SERVER SECTION
 2 # ----------------------------------------------------------------------
 3 #
 4 # The following options will be read by the MySQL Server. Make sure that
 5 # you have installed the server correctly (see above) so it reads this 
 6 # file.
 7 #
 8 [mysqld]
 9 
10 # The TCP/IP Port the MySQL Server will listen on
11 port=3306
12 
13 
14 #Path to installation directory. All paths are usually resolved relative to this.
15 basedir="E:/Java/Mysql/"
16 
17 #Path to the database root
18 datadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/"
19 
20 # The default character set that will be used when a new schema or table is
21 # created and no character set is defined
22 character-set-server=gb2312
23 
24 # The default storage engine that will be used when create new tables when
25 default-storage-engine=INNODB
26 
27 # Set the SQL mode to strict
28 sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
29 
30 # The maximum amount of concurrent sessions the MySQL server will
31 # allow. One of these connections will be reserved for a user with
32 # SUPER privileges to allow the administrator to login even if the
33 # connection limit has been reached.
34 max_connections=100
35 
36 # Query cache is used to cache SELECT results and later return them
37 # without actual executing the same query once again. Having the query
38 # cache enabled may result in significant speed improvements, if your
39 # have a lot of identical queries and rarely changing tables. See the
40 # "Qcache_lowmem_prunes" status variable to check if the current value
41 # is high enough for your load.
42 # Note: In case your tables change very often or if your queries are
43 # textually different every time, the query cache may result in a
44 # slowdown instead of a performance improvement.
45 query_cache_size=0
46 
47 # The number of open tables for all threads. Increasing this value
48 # increases the number of file descriptors that mysqld requires.
49 # Therefore you have to make sure to set the amount of open files
50 # allowed to at least 4096 in the variable "open-files-limit" in
51 # section [mysqld_safe]
52 table_cache=256
53 
54 # Maximum size for internal (in-memory) temporary tables. If a table
55 # grows larger than this value, it is automatically converted to disk
56 # based table This limitation is for a single table. There can be many
57 # of them.
58 tmp_table_size=35M
59 
60 
61 # How many threads we should keep in a cache for reuse. When a client
62 # disconnects, the client‘s threads are put in the cache if there aren‘t
63 # more than thread_cache_size threads from before.  This greatly reduces
64 # the amount of thread creations needed if you have a lot of new
65 # connections. (Normally this doesn‘t give a notable performance
66 # improvement if you have a good thread implementation.)
67 thread_cache_size=8
68 
69 #*** MyISAM Specific options
70 
71 # The maximum size of the temporary file MySQL is allowed to use while
72 # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
73 # If the file-size would be bigger than this, the index will be created
74 # through the key cache (which is slower).
75 myisam_max_sort_file_size=100G
76 
77 # If the temporary file used for fast index creation would be bigger
78 # than using the key cache by the amount specified here, then prefer the
79 # key cache method.  This is mainly used to force long character keys in
80 # large tables to use the slower key cache method to create the index.
81 myisam_sort_buffer_size=69M
82 
83 # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
84 # Do not set it larger than 30% of your available memory, as some memory
85 # is also required by the OS to cache rows. Even if you‘re not using
86 # MyISAM tables, you should still set it to 8-64M as it will also be
87 # used for internal temporary disk tables.
88 key_buffer_size=55M
89 
90 # Size of the buffer used for doing full table scans of MyISAM tables.
91 # Allocated per thread, if a full scan is needed.
92 read_buffer_size=64K
93 read_rnd_buffer_size=256K
94 
95 # This buffer is allocated when MySQL needs to rebuild the index in
96 # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
97 # into an empty table. It is allocated per thread so be careful with
98 # large settings.
99 sort_buffer_size=256K

上面是服务器断参数，一下是参数的简介：

　　1.port参数也是表示数据库的端口。

　　2.basedir参数表示MySQL的安装路径。

　　3.datadir参数表示MySQL数据文件的存储位置，也是数据库表的存放位置。

　　4.default-character-set参数表示默认的字符集，这个字符集是服务器端的。

　　5.default-storage-engine参数默认的存储引擎。

　　6.sql-mode参数表示SQL模式的参数，通过这个参数可以设置检验SQL语句的严格程度。

　　7.max_connections参数表示允许同时访问MySQL服务器的最大连接数，其中一个连接是保留的，留给管理员专用的。

　　8.query_cache_size参数表示查询时的缓存大小，缓存中可以存储以前通过select语句查询过的信息，再次查询时就可以直接从缓存中拿出信息。

　　9.table_cache参数表示所有进程打开表的总数。

　　10.tmp_table_size参数表示内存中临时表的总数。

　　11.thread_cache_size参数表示保留客户端线程的缓存。

　　12.myisam_max_sort_file_size参数表示MySQL重建索引时所允许的最大临时文件的大小。

　　13.myisam_sort_buffer_size参数表示重建索引时的缓存大小。

　　14.key_buffer_size参数表示关键词的缓存大小。

　　15.read_buffer_size参数表示MyISAM表全表扫描的缓存大小。

　　16.read_rnd_buffer_size参数表示将排序好的数据存入该缓存中。

　　17.sort_buffer_size参数表示用于排序的缓存大小

 

 

 1 #*** INNODB Specific options ***
 2 
 3 
 4 # Use this option if you have a MySQL server with InnoDB support enabled
 5 # but you do not plan to use it. This will save memory and disk space
 6 # and speed up some things.
 7 #skip-innodb
 8 
 9 # Additional memory pool that is used by InnoDB to store metadata
10 # information.  If InnoDB requires more memory for this purpose it will
11 # start to allocate it from the OS.  As this is fast enough on most
12 # recent operating systems, you normally do not need to change this
13 # value. SHOW INNODB STATUS will display the current amount used.
14 innodb_additional_mem_pool_size=3M
15 
16 # If set to 1, InnoDB will flush (fsync) the transaction logs to the
17 # disk at each commit, which offers full ACID behavior. If you are
18 # willing to compromise this safety, and you are running small
19 # transactions, you may set this to 0 or 2 to reduce disk I/O to the
20 # logs. Value 0 means that the log is only written to the log file and
21 # the log file flushed to disk approximately once per second. Value 2
22 # means the log is written to the log file at each commit, but the log
23 # file is only flushed to disk approximately once per second.
24 innodb_flush_log_at_trx_commit=1
25 
26 # The size of the buffer InnoDB uses for buffering log data. As soon as
27 # it is full, InnoDB will have to flush it to disk. As it is flushed
28 # once per second anyway, it does not make sense to have it very large
29 # (even with long transactions).
30 innodb_log_buffer_size=2M
31 
32 # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
33 # row data. The bigger you set this the less disk I/O is needed to
34 # access data in tables. On a dedicated database server you may set this
35 # parameter up to 80% of the machine physical memory size. Do not set it
36 # too large, though, because competition of the physical memory may
37 # cause paging in the operating system.  Note that on 32bit systems you
38 # might be limited to 2-3.5G of user level memory per process, so do not
39 # set it too high.
40 innodb_buffer_pool_size=107M
41 
42 # Size of each log file in a log group. You should set the combined size
43 # of log files to about 25%-100% of your buffer pool size to avoid
44 # unneeded buffer pool flush activity on log file overwrite. However,
45 # note that a larger logfile size will increase the time needed for the
46 # recovery process.
47 innodb_log_file_size=54M
48 
49 # Number of threads allowed inside the InnoDB kernel. The optimal value
50 # depends highly on the application, hardware as well as the OS
51 # scheduler properties. A too high value may lead to thread thrashing.
52 innodb_thread_concurrency=18

上面是InnoDB存储引擎使用的参数，一下是参数的简介：

　　1.innodb_additional_mem_pool_size参数表示附加的内存池，用来存储InnoDB表的内容。

　　2.innodb_flush_log_at_trx_commit参数是设置提交日志的时机，若设置为1，InnoDB会在每次提交后将事务日志写到磁盘上。

　　3.innodb_log_buffer_size参数表示用来存储日志数据的缓存区的大小。

　　4.innodb_buffer_pool_size参数表示缓存的大小，InnoDB使用一个缓冲池类保存索引和原始数据。

　　5.innodb_log_file_size参数表示日志文件的大小。

　　6.innodb_thread_concurrency参数表示在InnoDB存储引擎允许的线程最大数。

 

注意：每次修改参数后，必须重新启动MySQL服务才会有效。