source/adminguide/locale/zh_CN/LC_MESSAGES/events.mo (21 lines of code) (raw):
�� = � � � � � w b c � � � � � � �
* � 4
) 7 i O 8 � ( � T
p
�
�
� �
P j b � % - D r 1 � � � �
; \ { $ � � o � J ? 6 � ( � F � � 1 I � H � X < F F \ E � = � D ' & l a � � � Z � # E b i 4 � @ R B � � b j c � 1! ! P# � r# � �# t �% � & �& � �& ]' d' T z' L �' ( 3 8( l( ( �( M �( 6 �* B + ' a+ 1 �+ �+ ) �+ , " , +, K, R, | Y, �- �- �- . b .. H �. - �. / < '/ � d/ F W1 G �1 � �1 �2 �2 3 �2 9 3 ' Y3 * �3 �3 Q �3 � 4 X �5 ' '6 D O6 ' �6 / �6 A �6 **alert.purge.delay**: The alerts older than specified number of days are purged. Set the value to 0 to never purge alerts automatically. **alert.purge.interval**: The interval in seconds to wait before running the alert purge thread. The default is 86400 seconds (one day). A new event for state change, resource state change, is introduced as part of Event notification framework. Every resource, such as user VM, volume, NIC, network, public IP, snapshot, and template, is associated with a state machine and generates events as part of the state change. That implies that a change in the state of a resource results in a state change event, and the event is published in the corresponding state machine on the event bus. All the CloudStack events (alerts, action events, usage events) and the additional category of resource state change events, are published on to the events bus. A sample bean is given below: AMQP plug-in can place all the events on the a message queue, then a AMQP message broker can provide topic-based notification to the subscribers. An event is essentially a significant or meaningful change in the state of both virtual and physical resources associated with a cloud environment. Events are used by monitoring systems, usage and billing systems, or any other event-driven workflow systems to discern a pattern and make the right business decision. In CloudStack an event could be a state change of virtual or physical resources, an action performed by an user (action events), or policy based events (alerts). Archived alerts or events cannot be viewed in the UI or by using the API. They are maintained in the database for auditing or compliance purposes. As a CloudStack administrator, perform the following one-time configuration to enable event notification framework. At run time no changes can control the behaviour. Click OK. CloudStack provides you the ability to delete or archive the existing alerts and events that you no longer want to implement. You can regularly delete or archive any alerts or events that you cannot, or do not want to resolve from the database. Configuration Consider the following: Database logs can be queried from the user interface. The list of events captured by the system includes: Define a bean named ``eventNotificationBus`` as follows: Deleting and Archiving Events and Alerts ERROR. This event is generated when an operation has not been successfully performed Event Log Queries Event Logs Event Notification Event notification framework provides a means for the Management Server components to publish and subscribe to CloudStack events. Event notification is achieved by implementing the concept of event bus abstraction in the Management Server. An event bus is introduced in the Management Server that allows the CloudStack components and extension plug-ins to subscribe to the events by using the Advanced Message Queuing Protocol (AMQP) client. In CloudStack, a default implementation of event bus is provided as a plug-in that uses the RabbitMQ AMQP client. The AMQP client pushes the published events to a compatible AMQP server. Therefore all the CloudStack events are published to an exchange in the AMQP server. INFO. This event is generated when an operation has been successfully performed. In order to support the delete or archive alerts, the following global parameters have been added: In the left navigation, click Events. Log in as administrator to the CloudStack UI. Long Running Job Events Network/load balancer rules creation and deletion Notification Open ``'componentContext.xml``. Perform either of the following: Permissions Procedure Publish and Subscribe notification service can be implemented as a pluggable service in CloudStack that can provide rich set of APIs for event notification, such as topics-based subscription and notification. Additionally, the pluggable service can deal with multi-tenancy, authentication, and authorization issues. Restart the Management Server. Standard Events Storage volume creation and deletion Template creation and deletion The ``eventNotificationBus`` bean represents the ``org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus`` class. The domain admin or end user can delete or archive one or multiple events. The events log records three types of standard events. The following are some of the use cases: The root admin can delete or archive one or multiple alerts or events. There are two types of events logged in the CloudStack Event Log. Standard events log the success or failure of an event and can be used to identify jobs or processes that have failed. There are also long running job events. Events for asynchronous jobs log when a job is scheduled, when it starts, and when it completes. Other long running synchronous jobs log when a job starts, and when it completes. Long running synchronous and asynchronous event logs can be used to gain more information on the status of a pending job or can be used to identify a job that is hanging or has not started. The following sections provide more information on these events.. To archive events, click Archive Events, and specify event type and date. To archive events, click Delete Events, and specify event type and date. Usage or Billing Engines: A third-party cloud usage solution can implement a plug-in that can connects to CloudStack to subscribe to CloudStack events and generate usage data. The usage data is consumed by their usage software. Use Cases User login and logout Virtual machine creation, deletion, and on-going management operations Virtual router creation, deletion, and on-going management operations WARN. This event is generated in the following circumstances. When a network is disconnected while monitoring a template download. When a template download is abandoned. When an issue on the storage server causes the volumes to fail over to the mirror storage server. You can delete or archive individual alerts or events either directly by using the Quickview or by using the Details page. If you want to delete multiple alerts or events at the same time, you can use the respective context menu. You can delete alerts or events by category for a time period. For example, you can select categories such as **USER.LOGOUT**, **VM.DESTROY**, **VM.AG.UPDATE**, **CONFIGURATION.VALUE.EDI**, and so on. You can also view the number of events or alerts archived or deleted. exchange : The exchange name on the RabbitMQ server where CloudStack events are published. name : Specify a name for the bean. password : The password associated with the username of the account to access the RabbitMQ server. port : The port on which RabbitMQ server is running. server : The name or the IP address of the RabbitMQ AMQP server. username : The username associated with the account to access the RabbitMQ server. Project-Id-Version: Apache CloudStack Administration RTD
Report-Msgid-Bugs-To:
POT-Creation-Date: 2014-06-30 12:52+0200
PO-Revision-Date: 2014-06-30 12:04+0000
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Language: zh_CN
Plural-Forms: nplurals=1; plural=0;
**alert.purge.delay** : 指定报警大于多少天被销毁。设置值为0将永不自动销毁 **alert.purge.interval** : 执行销毁线程后等待间隔秒数. 默认值是86400秒 ( 1天 ). 状态变化，资源状态变化的新事件作为事件通知架构的一部分被引入。每个资源，例如用户VM，卷VM，网卡，网络，公共IP，快照以及模板，使用机器状态和常规事件被关联起来作为状态变化的一部分。这意味着，一个资源状态的变化产生了一个状态变化事件，并且该事件被公布到相应的状态事件总线。所有的 CloudStack 事件（报警，动作事件，使用事件）和 资源状态变化事件的附加条目将被公布到事件总线。 下面给出一个实体实例： AMQP的插件可以存放消息队列中的所有事件，然后一个AMQP消息代理可以提供基于主题的通知订阅者。 事件本质上是与云环境相关的虚拟和物理资源的状态显著或有意义的变化。事件用于监控系统，使用率和计费系统，或者是用于辨别模式和做出正确商业决定的其他任何事件驱动工作流系统。在 CloudStack 中的事件可以是虚拟或物理资源的状态变化，用户（操作事件）执行的操作，或基于策略的事件（警告）。 不能同通过UI 或 API 来归档报警或者事件。它们都存放在数据库中用于升级或其他目的。 作为一个 CloudStack 管理员，执行下列一次性配置启用事件通知框架。在运行时不能修改控件行为。 点击确定。 CloudStack 提供你删除或归档那些再也不使用的现存警告和事件的能力。您可以定期删除或存档的任何那些您不能或不想从数据库来解决的警报或事件， 配置 参考以下几点： 可以通过用户接口查询数据库日志。系统收集了以下列表事件： 按照以下实例顶一个叫做 “ eventNotificationBus ” 的实体： 删除和归档事件警告 错误：当操作没有成功执行产生该事件 事件记录查询 事件日志 事件通知 事件通知框架提供一种手段来管理管理服务器组件来发布和订阅 CloudStack 中的事件。事件通知是通过实现事件总线抽象的管理服务器的概念来实现。事件总线的管理服务器，允许 CloudStack 中的组件和扩展插件通过使用高级消息队列协议（AMQP）客户端订阅事件的介绍。在 CloudStack 中，事件总线默认通过一个使用Rabbit MQAMQP 客户端 的插件实现。AMQP 客户端推送发布事件到兼容 AMQP 服务器。因此，所有的 CloudStack 中的事件发布到 AMQP 服务器中交换 。 通知：当一个操作被成功执行产生事件。 为了支持删除或归档报警，增加了以下全局参数： 在左侧导航栏中，点击事件。 使用管理员登录到CloudStack管理界面。 长事件运行任务事件 网络/压力 负载规则创建和删除 通知 打开 `` componentContext.xml ``. 请执行下列操作之一： 许可 步骤 AMQP的插件可以存放所有事件在一个消息队列中，然后AMQP打乱的
发布和订阅通知服务可以作为一个可插拔的服务，在CloudStack中该服务可以为事件通知提供丰富的API集，如主题为标题的主题和通知。此外，可插拔服务可以处理多租户，认证，授权issues.age代理，并提供基于主题的订阅通知。 重启管理服务器。 标准事件 存储卷创建和和删除 模板创建和删除 `` eventNotificationBus `` 表示 ` `org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus `` 类 域关乎或终端用户可以删除或归档一个或多个警告事件 事件日志记录三种类型的标准事件 以下是一些使用场景： root 管理 可以删除或归档一个或多个警告事件 这里有两种类型的事件记录在&PRODUCT;事件日志。标准事件记录一个事件的成功或失败，并且可以用于鉴别哪些是已经失败的任务或进程。这里也记录长时间运行任务事件。异步任务的制定，启动，完成这些事件都被记录。长时间运行的同步和异步事件日志可用于获取挂起任务更多的状态信息，也可以用来识别任务是被挂起或还未开始。以下各节提供有关这些事件的详细信息。 归档事件，点击 归档事件，并指定事件类型和日期。 归档事件，点击 删除事件，并指定事件类型和日期。 使用率或计费引擎：第三方云使用的解决方案可以实现一个插件，它可以连接到 CloudStack 中订阅 CloudStack 中的事件并产生使用率数据。使用率数据是它们的使用的软件消耗。 使用案例 用户登录注销 虚拟机创建，删除，以及持续管理操作 虚拟路由器创建，删除，以及持续管理操作 警告：以下状况产生该事件。 监控模板下载的同时网络被断开 模板下载被放弃 当存储服务器上的问题会导致卷故障转移到镜像存储服务器。 您可以通过快速查看或详情页面直接删除或归档个别警报或事件。如果你想同时删除多个警报或事件，您可以分别使用相应的快捷菜单。您可以按类别删除某个时期的警报或事件。例如，您可以选择诸如 ** USER.LOGOUT**，** VM.DESTROY**，** VM.AG.UPDATE**，** CONFIGURATION.VALUE.EDI** 等类别，依此类推。您还可以查看事件和警报归档或删除的数量。 交流：其中 CloudStack 中事件发布的 RabbitMQ 的服务器上的交流名称。 名字：为实体指定一个名字。 密码： 密码关联访问 RabbitMQ 服务器账号的用户名。 端口 : RabbitMQ服务器运行端口. 服务器： RabbitMQ AMQP 的名字或IP地址 用户名： 用户名关联访问 RabbitMQ 服务器的账号。