- 浏览: 129718 次
- 性别:
- 来自: 福建省莆田市
文章分类
最新评论
-
houruiming:
tks for your info which helps m ...
setcontent和setcontentobject用的是同一片内存 -
turingfellow:
in.tftpd -l -s /home/tmp -u ro ...
commands -
turingfellow:
LINUX下的网络设置 ifconfig ,routeLINU ...
commands -
turingfellow:
安装 linux loopbackyum install um ...
commands
information an event carries assumes that events are composite objects able to carry
information,and so on.
The plan descriptors we use provide an identifier,the triggering event type,the
plan steps as well as a short natural language description,a context specification in-
dicating when this plan should be used and a list of data read and written.
Event descriptors are used to fully specify all events,including those identified ear-
lier.The event descriptor should identify the purpose of the event and any data that
the event carries.We also indicate for each event whether it is expected to be covered
and whether it is expected to be unambiguous.An event is covered if there is always at
least one handling plan which is applicable;that is,for any situation,at least one of the
matching plans will have a true context condition.An event is unambiguous if there is
always at most one handling plan which is applicable.
Data descriptors should specify the fields and methods of any classes used for data
storage within the system.If specialised data structures are provided for maintaining
beliefs,these should also be specified.
An additional artifact that is completed(and checked)at this point is the data dic-
tionary.The data dictionary should be started at the beginning of the project and devel-
oped further at each stage.The data dictionary is important in ensuring consistent use
of names(for example,what is called“delivery info”in one place in the design should
not be called“deliv.information”elsewhere).One option is to organise the data dic-
tionary into separate sections for agents,capabilities,plans,events and data,organised
alphabetically within sections.The other option is to have a flat alphabetical structure.
With tool support multiple views(automatically generated)can be provided.
5 Discussion and conclusions
We have briefly described the key aspects of the Prometheus methodology.The method-
ology has been in use for several years and has been taught in industry workshops(most
recently at the Australian AI conference,2001).The methodology has been in use for
several years as a teaching tool.The feedback we have received indicates that it provides
substantial guidance for the process of developing the design and for communicating
the design within a work group.With student projects it is abundantly clear that the
existence of the methodology is an enormous help in thinking about and deciding on
the design issues,as well as conveying the design decisions.
One of the advantages of this
methodology is the number of places
where automated tools can be used for
consistency checking across the vari-
ous artifacts of the design process.For
example,the input and output events
for an agent must be the same on the
system overview diagram and on the
agent overview diagram.Agent Ori-
ented Software has constructed a sup-
port tool for the methodology that al-
lows design diagrams to be drawn and generates corresponding skeleton code(in
JACK).
We are also investigating how some of the design artifacts,such as the protocol
definitions,and the capability diagrams,can be used for providing debugging and trac-
ing support within the implemented system[21].Having a design methodology which
can be used through to testing and debugging is clearly advantageous in terms of an
integrated and complete methodology.
Other areas for future work include:clearer integration of goals as a first class con-
cept,extensions to the graphical notation to allow percepts,actions,goals,and(some)
sequencing information to be specified;introduction of social concepts(teams,roles);
and investigating the commonalities and differences with various extensions of UML to
agents[19,20].Additionally,we intend to integrate Prometheus with the agent concepts
we have identified[26].
Acknowledgements:We would like to acknowledge the support of Agent Ori-
ented Software Pty.Ltd.and of the Australian Research Council(ARC)under grant
CO0106934.We would also like to thank James Harland and Jamie Curmi for com-
ments on drafts of this paper.
information,and so on.
The plan descriptors we use provide an identifier,the triggering event type,the
plan steps as well as a short natural language description,a context specification in-
dicating when this plan should be used and a list of data read and written.
Event descriptors are used to fully specify all events,including those identified ear-
lier.The event descriptor should identify the purpose of the event and any data that
the event carries.We also indicate for each event whether it is expected to be covered
and whether it is expected to be unambiguous.An event is covered if there is always at
least one handling plan which is applicable;that is,for any situation,at least one of the
matching plans will have a true context condition.An event is unambiguous if there is
always at most one handling plan which is applicable.
Data descriptors should specify the fields and methods of any classes used for data
storage within the system.If specialised data structures are provided for maintaining
beliefs,these should also be specified.
An additional artifact that is completed(and checked)at this point is the data dic-
tionary.The data dictionary should be started at the beginning of the project and devel-
oped further at each stage.The data dictionary is important in ensuring consistent use
of names(for example,what is called“delivery info”in one place in the design should
not be called“deliv.information”elsewhere).One option is to organise the data dic-
tionary into separate sections for agents,capabilities,plans,events and data,organised
alphabetically within sections.The other option is to have a flat alphabetical structure.
With tool support multiple views(automatically generated)can be provided.
5 Discussion and conclusions
We have briefly described the key aspects of the Prometheus methodology.The method-
ology has been in use for several years and has been taught in industry workshops(most
recently at the Australian AI conference,2001).The methodology has been in use for
several years as a teaching tool.The feedback we have received indicates that it provides
substantial guidance for the process of developing the design and for communicating
the design within a work group.With student projects it is abundantly clear that the
existence of the methodology is an enormous help in thinking about and deciding on
the design issues,as well as conveying the design decisions.
One of the advantages of this
methodology is the number of places
where automated tools can be used for
consistency checking across the vari-
ous artifacts of the design process.For
example,the input and output events
for an agent must be the same on the
system overview diagram and on the
agent overview diagram.Agent Ori-
ented Software has constructed a sup-
port tool for the methodology that al-
lows design diagrams to be drawn and generates corresponding skeleton code(in
JACK).
We are also investigating how some of the design artifacts,such as the protocol
definitions,and the capability diagrams,can be used for providing debugging and trac-
ing support within the implemented system[21].Having a design methodology which
can be used through to testing and debugging is clearly advantageous in terms of an
integrated and complete methodology.
Other areas for future work include:clearer integration of goals as a first class con-
cept,extensions to the graphical notation to allow percepts,actions,goals,and(some)
sequencing information to be specified;introduction of social concepts(teams,roles);
and investigating the commonalities and differences with various extensions of UML to
agents[19,20].Additionally,we intend to integrate Prometheus with the agent concepts
we have identified[26].
Acknowledgements:We would like to acknowledge the support of Agent Ori-
ented Software Pty.Ltd.and of the Australian Research Council(ARC)under grant
CO0106934.We would also like to thank James Harland and Jamie Curmi for com-
ments on drafts of this paper.
发表评论
-
protocols
2011-04-03 19:22 878<!-- The protocols capabilit ... -
dfcap
2011-04-03 19:15 818<!-- The df capability has a ... -
booktrading /seller
2011-03-29 23:19 865<html><head><tit ... -
booktrading / manager
2011-03-29 23:18 1036<html><head><tit ... -
booktrading / common
2011-03-29 23:17 947<html><head><tit ... -
booktrading / buyer
2011-03-29 23:13 808<!-- <H3>The buyer age ... -
tomcat的context说明书
2011-03-20 17:39 759http://tomcat.apache.org/tomcat ... -
msyql的select语法
2010-09-13 22:52 103213.2.7. SELECT语法 13.2.7.1. ... -
zotero与word集成
2010-09-11 08:50 1685Manually Installing the Zotero ... -
university 2/n
2010-08-24 07:54 834Chapter 1.Introduction of regis ... -
university 1/n
2010-08-24 07:53 882chapter? Introduction ?.?The st ... -
Sun Java Bugs that affect lucene
2010-08-23 08:59 683Sometimes Lucene runs amok of b ... -
Snowball分词
2010-08-22 13:07 1161using System; using Lucene.Net. ... -
penn tree bank 6/6
2010-08-20 07:09 88411 This use of 12 Contact the - ... -
penn tree bank 5/n
2010-08-19 07:40 874always errs on the side of caut ... -
penn tree bank 4/n
2010-08-19 07:39 7844. Bracketing 4.1 Basic Methodo ... -
penn tree bank 3/n
2010-08-15 23:31 7712.3.1 Automated Stage. During t ... -
penn tree bank 2/n
2010-08-15 23:30 1450Mitchell P Marcus et al. Buildi ... -
capabilities 3/3
2010-08-11 22:58 73201<capability xmlns="ht ... -
capabilities 2/3
2010-08-11 22:57 696Fig.3.Element creation cases:a) ...
相关推荐
prometheus-2.17.0-rc.4.linux-amd64.tar.gz 压缩包下载,linux版本 该资源为prometheus-2.17* linux安装包,用于系统监控和报警。 prometheus是一个开源的监控和报警系统。从2012年初,很多 公司和组织开始使用...
Prometheus-2.33.4 Linux二进制安装包全家桶
二、Prometheus架构概览 4 三、Prometheus的数据模型 5 四、Prometheus四种数据类型 5 1.部署prometheus(普罗米修斯) 时序数据库 6 2.Master部署mysql_exporter 8 3.部署node_exporter 9 4.部署Grafana(格拉法娜) 9 ...
资源分类:Python库 所属语言:Python 资源全名:prometheus-api-client-0.0.2b4.tar.gz 资源来源:官方 安装方法:https://lanzao.blog.csdn.net/article/details/101784059
Prometheus技术讲义 1 1简介 1 2架构图 2 3 prometheus组件介绍 2 4基本原理 3 5服务过程 3 6部署 4 7度量类型 4 7.1、Counter(计数器类型) 4 7.2、Gauge(仪表测量类型) 4 7.3、Histogram(直方图类型) 5 7.4、...
"github.com/prometheus/client_golang/prometheus/promhttp" echoPrometheus "github.com/globocom/echo-prometheus" ) func main () { e := echo . New () e . Use ( echoPrometheus . MetricsMiddleware ()) ...
1: Prometheus-2.24.0安装包 2:grafana-7.3.6安装包 3:mysql监控安装 4: node_exporter安装包
4. 以拉模型推送时间序列数据:Prometheus 服务器定期从 exporters 或者 push gateways 抓取时间序列数据。 5. 目标发现:Prometheus 可以通过服务发现或者静态配置自动发现监控目标。 6. 可扩展性:一个 Prometheus ...
一、Prometheus的概念和发展史 Prometheus是一个开源的完整监控解决方案,本文将从指标抓取到查询及可视化展示,以及最后的监控告警,对Prometheus做一个基本的认识。...4.同时支持PushGateway组件收集数据
简单代理,提供来自HPE iLO 4的温度作为Prometheus指标。 仅在MicroServer Gen8上的2.70和2.75版本上进行了测试。 它需要具有读取权限的iLO帐户。 部署方式 在存储库可以找到舵图 要使用它,首先将其添加到存储库...
当前,可用的指标是: 集群状态节点状态: 虚拟机指数(全球) 运输HTTP 剧本过程操作系统文件系统断路器指数状态群集设置(仅适用于选定的)相容性矩阵版本7.X 弹性搜索插入发布日期7.12.0 7.12.0.0 2021年4月4日...
4. 安装并配置Grafana,创建仪表盘并添加Prometheus作为数据源,以便能够展示Elasticsearch的监控数据。 通过以上步骤大致实现使用Prometheus+Grafana对Elasticsearch进行监控和可视化的方案。这个方案不仅可以帮助...
PushProx PushProx是客户端和代理,允许Prometheus穿越NAT和其他类似的网络拓扑,同时仍然遵循拉模型。 尽管这在实践中相当可靠,但这是一项正在进行的工作。跑步首先构建代理和客户端: git clone ...
适用于Prometheus的VMWare VCenter导出器。 获取VMWare VCenter信息: 当前活动快照的数量 快照Unix时间戳记创建日期 数据存储区大小和其他内容 基本VM和主机指标 档案 请注意,该存储库不再维护。 请转到以获取...
官方离线安装包,亲测可用
Prometheus SRCDS出口商这是Prometheus监控系统的出口商。 它通过rcon从SRCDS游戏服务器(例如CSGO,TF2,L4D2等)导出数据。 为此,它使用status和stats命令。支持的服务器: 政务司司长CSS L4D2 FoF HL2DM TF2 格...
要使用python编写Prometheus监控,需要你先开启Prometheus集群。...在python中实现服务器端。在Prometheus中配置请求网址,Prometheus会定期向该网址发起申请...Prometheus提供4种类型Metrics:Counter, Gauge, Summary和
支持Redis 2.x,3.x,4.x,5.x和6.x建立并运行出口商在本地构建和运行git clone https://github.com/oliver006/redis_exporter.gitcd redis_exportergo build ../redis_exporter --version预编译二进制对于预构建的...
1.MetricServer:是kubernetes集群资源使用情况的聚合器,收集数据给kubernetes集群内使用,如 2.PrometheusOperat