1、The configuration file can be found in server/config/application.yml. Except for the MySQL database connection information (lines 18-20 of the configuration file) that needs to be modified, everything else is temporarily set to default and can be adjusted according to the actual scenario in the future

(1) Change the MySQL database connection information to your own actual information. More database connection configuration instructions

(2) Administrator account/password, default: admin/111111, You can change it to your favorite account and password, Default for now

(3) wgToken is the communication key between the server and agent, and the wgToken values in the server and agent configuration files should be consistent，Default for now

Pay attention to the yml file format rules, and leave an English space after the colon for each configuration item

Tips：If the firewall or security group of the server host is running, these two ports need to be released: 9999（Server web access port）、9998（Web SSH port, can be disabled without using web SSH），View the instructions for opening Linux firewall ports

server: port: 9999 servlet: session: timeout: 120m cookie: name: wgcloud-server #Log file output path logging: file: path: ./log # Database configuration spring: application: name: wgcloud-server datasource: driver-class-name: com.mysql.jdbc.Driver url: jdbc:mysql://localhost:3306/wgcloud?characterEncoding=utf-8&characterSetResults=utf8&autoReconnect=true&useSSL=false&allowMultiQueries=true username: root password: 123456 hikari: validationTimeout: 3000 connectionTimeout: 60000 idleTimeout: 60000 minimumIdle: 10 maximumPoolSize: 10 maxLifeTime: 60000 connectionTestQuery: select 1 mvc: static-path-pattern: /static/** thymeleaf: cache: false mybatis: config-location: classpath:mybatis/mybatis-config.xml mapper-locations: classpath:mybatis/mapper/*.xml #Custom configuration parameters base: #Administrator login account account: admin #Password of administrator accountPwd: 111111 #Does the login page need to display a verification code? yes is displayed, no is not displayed vercodeCheck: no #Whether to enable password free login, yes enable, no disable, this feature needs to be upgraded to the professional version when enabled openSSO: no #Communication token. The wgToken on the agent side is consistent with this wgToken: wgcloud #How many pieces of data are displayed on each page? It is recommended that it should not be less than 10 pageSize: 20 #Whether to enable the web ssh client, yes enable, no disable webSsh: yes #Service port of web ssh client webSshPort: 9998 #The daemon accesses the url, the server service uses it, and the agent does not use it (generally the default is enough) daemonUrl: http://localhost:9997 #Whether to open the public screen, yes to open, no to close, and no to login after opening the Kanban page dashView: yes #Whether the desensitization display is enabled for the host IP on the public signage page, yes is enabled, no is disabled dashViewIpHide: yes #Whether to open the large screen display board, yes to open, no to close, and the board page does not need to log in after opening dapingView: yes #Is the data open interface enabled? Yes enabled, no disabled openDataAPI: yes #Whether to automatically close the left menu, yes Yes, no No sidebarCollapse: yes #Whether to display alarm times on the list page, yes Yes, no No showWarnCount: no #Whether to enable the issuance of instructions (if it is closed, no more instructions can be added and issued), yes Yes, no No shellToRun: yes #Send command characters that cannot be included in command issuance can be lowercase, multiple characters can be used, separated by shellToRunBlock: 'rm ,mkfs, /dev/,:(){:|:&};:,mv ,wget , install ,del ,delete ,format ,ren ,rd ,rd/s/q ,rmdir ' #The SQL statement for data monitoring cannot be used to write sensitive characters (i.e. keywords that may be injected into SQL), which can be lowercase and separated by commas sqlInKeys: 'execute ,update ,delete ,insert ,create ,drop ,alter ,rename ,modify ' #Data table monitoring interval, in seconds, 60 minutes by default dbTableTimes: 3600 #API monitoring interval, in seconds, 10 minutes by default heathTimes: 600 #FTP/SFTP service monitoring interval, in seconds, default to 10 minutes ftpTimes: 600 #PING monitoring interval of data communication equipment, unit: second, default: 15 minutes dceTimes: 900 #Snmp monitoring interval of data communication device, unit: second, default: 20 minutes snmpTimes: 1200 #Alarm buffer interval (the same alarm notification will not be sent repeatedly within this period), unit: second, default: 120 minutes warnCacheTimes: 7200 #Monitoring data retention days, 30 days by default historyDataOut: 30 #Monitoring data trend line chart, with the maximum amount of data displayed per query for each chart. If the amount of data exceeds this value, the system will automatically balance and process the data. The final amount of data retained is equal to this value #This is mainly to prevent the chart from displaying too much data at once and causing browser lag. Setting it to 0 indicates that the balance processing is not compressed chartDataMaxShowValue: 4000 #The node type (only used by the cluster, which is generally the default), master or slave. A cluster can only have one master and N (31 at most) slave, such as: slave1,slave2 nodeType: master #Whether to enable label management, yes enable, no disable hostGroup: no #Whether to enable member account management (that is, each member can manage its own resources). Yes is enabled and no is closed. After closing, #new members cannot log in again (administrators and read-only accounts can log in). This function needs to be upgraded to the pro-version userInfoManage: no #The icon name of ico under server/logo/, 32 * 32, such as favicon.png, which needs to be upgraded to pro-version icoName: #The logo icon name under server/logo/, 120 * 120, such as logo.png, which needs to be upgraded to the pro-version logoName: #System name, such as wgcloud operation and maintenance monitoring system, which needs to be upgraded to pro-version wgName: #System abbreviation, such as wgcloud, which needs to be upgraded to the pro-version wgShortName: #Alarm mail title prefix, this function needs to be upgraded to the pro-version mailTitlePrefix: '[WGCLOUD]' #Suffix of alarm email content, this function needs to be upgraded to pro-version mailContentSuffix: '<p><p><p>WGCLOUD' #Whether to display the copyright and website information at the bottom of the page. Yes is displayed, no is not displayed. #This function needs to be upgraded to the pro-version copyRight: yes ......

 

The above is only a part of the configuration file server/config/application.yml. The remaining part is not displayed because it does not need to be modified during the installation and deployment process. It can be customized according to the actual scenario in the future

 

Previous Step    Next Step