Enable jmx monitoring что это

server.properties

Файл server.properties по умолчанию для Java Edition.

server.properties — это файл, в котором хранятся все настройки для многопользовательского ( Minecraft или Minecraft Classic) сервера.

Если server.properties не перечисляет все свойства (например, если новая версия сервера добавляет новые свойства или файл не существует), то при запуске сервер перезаписывает файл server.properties с новыми перечисленными свойствами и установите для них значения по умолчанию.

Файл server.properties представляет собой обычный текстовый файл с кодировкой UTF-8, несмотря на то, что он расширение, и поэтому его можно редактировать с помощью любого текстового редактора, такого как Блокнот для Windows, TextEdit для Mac или nano и vim для Linux.

Расположение файла

Java Edition

Этот файл автоматически создается при первом запуске сервера (если он не существует).

Bedrock Edition

Значения соотносятся с целочисленными режимами игры следующим образом:

Minecraft Свойства классического сервера

Примечание: Если установлено больше 3, оно меняется обратно на 3.

Источник

Apache Tomcat 7

Links

User Guide

Reference

Apache Tomcat Development

Monitoring and Managing Tomcat

Monitoring is a key aspect of system administration. Looking inside a running server, obtaining some statistics or reconfiguring some aspects of an application are all daily administration tasks.

Note: This configuration is needed only if you are going to monitor Tomcat remotely. It is not needed if you are going to monitor it locally, using the same user that Tomcat runs with.

The Oracle website includes the list of options and how to configure JMX Remote on Java 8: http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html.

The following is a quick configuration guide for Java 8:

Add the following parameters to setenv.bat script of your Tomcat (see RUNNING.txt for details).
Note: This syntax is for Microsoft Windows. The command has to be on the same line. It is wrapped to be more readable. If Tomcat is running as a Windows service, use its configuration dialog to set java options for the service. For Linux, MacOS, etc, remove «set » from beginning of the line.

If you don’t set com.sun.management.jmxremote.rmi.port then the JSR 160 JMX-Adaptor will select a port at random which will may it difficult to configure a firewall to allow access.

If you require TLS:

If you require authorization (it is strongly recommended that TLS is always used with authentication):

If you need to specify a host name to be used in the RMI stubs sent to the client (e.g. because the public host name that must be used to connect is not the same as the local host name) then you can set:

If you need to specify a specific interface for the JMX service to bind to then you can set:

To simplify JMX usage with Ant, a set of tasks is provided that may be used with antlib.

The following example shows the JMX Accessor usage:
Note: The name attribute value was wrapped here to be more readable. It has to be all on the same line, without spaces.

import: Import the JMX Accessor Project with and reference the tasks with jmxOpen, jmxSet, jmxGet, jmxQuery, jmxInvoke, jmxEquals and jmxCondition.

Example to open a new JMX connection

Example to open a JMX connection from URL, with authorization and store at other reference

Example to open a JMX connection from URL, with authorization and store at other reference, but only when property jmx.if exists and jmx.unless not exists

Note: All properties from jmxOpen task also exists at all other tasks and conditions.

Example to get remote MBean attribute from default JMX connection

Example to get and result array and split it at separate properties

Example to get IDataSender attribute connected only when cluster is configured.
Note: The name attribute value was wrapped here to be more readable. It has to be all on the same line, without spaces.

Example to set remote MBean attribute value

stop an application

Example to get all sessionids

Example to create a new access logger valve at vhost localhost

Now you can find new MBean with name stored at $ property.

Get all Manager ObjectNames from all services and Hosts

Example to get the Manager from servlet-examples application an bind all MBean properties

Example to get all MBeans from a server and store inside an external XML property file

Now you can find all MBeans inside the file mbeans.properties.

Example to create remote MBean

Warning: Many Tomcat MBeans can’t be linked to their parent once
created. The Valve, Cluster and Realm MBeans are not automatically
connected with their parent. Use the MBeanFactory create
operation instead.

Example to unregister remote MBean

Warning: A lot of Tomcat MBeans can’t be unregister.
The MBeans are not unlinked from their parent. Use MBeanFactory
remove operation instead.

Wait for server connection and that cluster backup node is accessible

Wait for server connection and that cluster backup node is accessible

Tomcat offers an alternative to using remote (or even local) JMX connections while still giving you access to everything JMX has to offer: Tomcat’s JMXProxyServlet.

The JMXProxyServlet allows a client to issue JMX queries via an HTTP interface. This technique offers the following advantages over using JMX directly from a client program:

A perfect example of JMX overkill can be seen in the case of popular server-monitoring software such as Nagios or Icinga: if you want to monitor 10 items via JMX, you will have to launch 10 JVMs, make 10 JMX connections, and then shut them all down every few minutes. With the JMXProxyServlet, you can make 10 HTTP connections and be done with it.

You can find out more information about the JMXProxyServlet in the documentation for the Tomcat manager.

Источник

Zabbix: мониторинг Tomcat с помощью JMX

Что такое JMX (Java Management eXtensions) хорошо описано тут>>>.

Наша задача – запустить Tomcat с поддержкой JMX, настроить Java-gateway для сервера Zabbix, добавить набор элементов данных для мониторинга Tomcat и связать его с существующим шаблоном.

Убедимся, что на самом Zabbix-сервере zabbix-java-gateway работает:

По-умолчанию Java-gateway слушает порт 10052 :

В случае проблем – ведётся отдельный лог-файл:

В файле конфигурации сервера /etc/zabbix/zabbix_server.conf настраиваем соединения и опции запуска Java-gateway :

Переходим к наблюдаемому хосту. Настроим Tomcat для запуска с поддержкой JMX.

Теперь Tomcat запущен с поддержкой JMX, и прослушивает порт 8004 :

Теперь – добавим хост под наблюдение сервера.

Переходим в Configuration > Hosts, кликаем Create host:

Заполняем поля Agent interfaces и JMX interfaces, переходим во вкладку Teamplates и выбираем Template JMX Tomcat:

Возвращаемся к списку хостов и видим что иконка JMX зелёная. Бывает, что требуется несколько минут, что бы Java-gateway смог установить соединение и отобразить состояние:

У нас есть уже готовые графики в шаблонах, можно на них посмотреть. Переходим в Monitoring > Graphs, выбираем хост и интересующий график, наблюдаем:

На этом настройку мониторинга Java-приложения с помощью Zabbix через JMX можно считать выполненным.

В следующий раз мы добавим свои элементы данных (items) и триггеры (triggers).

Источник

Administering Jira applications Support

Products

Jira Software

Project and issue tracking

Jira Service Management

Service management and customer support

Jira Core

Manage any business project

Confluence

Bitbucket

Git code management

Resources

Documentation

Usage and admin help

Community

Answers, support, and inspiration

Suggestions and bugs

Feature suggestions and bug reports

Marketplace

Billing and licensing

Frequently asked questions

Viewport

Confluence

Versions

Live monitoring using the JMX interface

System administration

On this page

Related content

Still need help?

The Atlassian Community is here for you.

This article describes how to expose JMX MBeans within Jira for monitoring with a JMX client.

This guide provides a basic introduction to the JMX interface and is provided as is. Our support team can help you troubleshoot a specific Jira problem, but aren’t able to help you set up your monitoring system or interpret the results.

What is JMX?

JMX attribute name

The value at the 50th percentile in the distribution of measured times (the median value).

The value at the 75th percentile in the distribution of measured times.

The value at the 95th percentile in the distribution of measured times.

The value at the 98th percentile in the distribution of measured times.

The value at the 99th percentile in the distribution of measured times.

The value at the 99.9th percentile in the distribution of measured times.

The number of invocations since node startup.

The time unit used to report percentile values, min, max, mean and standard deviation. Default is milliseconds.

The fifteen-minute moving average rate of invocations since node startup. This rate uses the same exponential decay factor as is used for the fifteen minute load average in Unix’s top command.

The five-minute moving average rate of invocations since node startup. This rate uses the same exponential decay factor as is used for the five minute load average in Unix’s top command.

The highest measured time since node startup.

The mean measured time since node startup.

The mean rate of invocations since node startup.

The lowest measured time since node startup.

The one-minute moving average rate of invocations since node startup. This rate uses the same exponential decay factor as is used for the one minute load average in Unix’s top command.

The unit in which MeanRate, OneMinuteRate, FiveMinuteRate and FifteenMinuteRate are reported. Default is events / second.

The standard deviation in the measured times since node startup.

Metrics collected by Jira

The following table lists metrics (MBeans) that are collected by Jira. All of them are grouped in the com.atlassian.jira property.

The number of times all dashboards were viewed by users.