Hawkular Metrics 不会被带到 Grafana Web 控制台
Hawkular Metrics not be brought to Grafana web console
我的 OS 是 CentOS 7 和 运行 Wildfly 10.1。监控工具是Hawkular 0.39.0和Grafana server 3.1.1。我修改了Hawkular和Wildfly的具体IP。以下是日志内容
鹰派
18:19:01,601 INFO [org.hawkular.metrics.core.dropwizard.MetricsInitializer] (RxComputationScheduler-1) Finished creating metrics in 702 ms
18:19:01,721 WARN [com.datastax.driver.core.Cluster] (cluster2-worker-0) Re-preparing already prepared query is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once. Query='SELECT DISTINCT tenant_id, tname FROM metrics_tags_idx'
18:19:01,803 INFO [org.hawkular.metrics.core.util.GCGraceSecondsManager] (metricsservice-lifecycle-thread) Checking tables in hawkular_metrics to see if gc_grace_seconds needs to be updated
18:19:01,811 INFO [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle] (metricsservice-lifecycle-thread) HAWKMETRICS200005: Metrics service started
18:19:01,830 INFO [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-3) Finished gc_grace_seconds updates in 26 ms
18:19:02,081 INFO [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (Hawkular Java Agent Start Thread) HAWKMONITOR010039: The command-gateway URL is [ws://192.168.200.51:8080/hawkular/command-gateway/feed/localhost]
18:19:02,148 INFO [org.hawkular.agent.monitor.scheduler.SchedulerService] (Hawkular Java Agent Start Thread) HAWKMONITOR010012: Starting scheduler
18:19:02,148 INFO [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (OkHttp http://192.168.200.51:8080/...) HAWKMONITOR010034: Opened feed WebSocket connection to endpoint [ws://192.168.200.51:8080/hawkular/command-gateway/feed/localhost]
18:19:02,195 INFO [org.apache.activemq.artemis.ra] (default-threads - 4) AMQ151000: awaiting topic/queue creation HawkularQueue
18:19:02,200 INFO [org.hawkular.agent.monitor.protocol.ProtocolServices] (Hawkular Java Agent Start Thread) HAWKMONITOR010019: Managed server [Local DMR] is disabled. It will not be monitored.
18:19:02,228 INFO [org.apache.activemq.artemis.ra] (default-threads - 2) AMQ151000: awaiting topic/queue creation HawkularCommandEvent
18:19:02,239 INFO [org.hawkular.cmdgw.command.ws.server.FeedWebSocket] (default task-7) HAWKFEEDCOMM000013: WebSocket session [localhost] opened for endpoint [/feed/{feedId}]
18:19:02,328 INFO [org.xnio] (Hawkular Java Agent Start Thread) XNIO version 3.3.4.Final
野蝇 10.1
18:18:55,599 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 11438ms - Started 894 of 1172 services (470 services are lazy, passive or on-demand)
18:18:55,603 INFO [org.hawkular.agent.monitor.service.AgentCoreEngine] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR010084: Hawkular Agent: WildFly Agent Subsystem version 1.0.0.CR6
18:18:55,632 INFO [org.hawkular.agent.monitor.service.AgentCoreEngine] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR010000: Starting Hawkular Agent
18:18:55,632 INFO [org.hawkular.agent.monitor.service.MonitorService] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR020059: Agent is using storage adapter mode [HAWKULAR]
18:18:55,632 INFO [org.hawkular.agent.monitor.service.MonitorService] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR020050: Tenant ID [hawkular]
18:18:55,654 INFO [org.hawkular.agent.monitor.service.MonitorService] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR020025: Will talk to Hawkular at URL [http://192.168.200.51:8080]
18:19:06,777 INFO [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR010039: The command-gateway URL is [ws://192.168.200.51:8080/hawkular/command-gateway/feed/51491521-cdcb-4d11-9869-676b06491c8e]
18:19:06,793 INFO [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (OkHttp http://192.168.200.51:8080/...) HAWKMONITOR010034: Opened feed WebSocket connection to endpoint [ws://192.168.200.51:8080/hawkular/command-gateway/feed/51491521-cdcb-4d11-9869-676b06491c8e]
18:19:06,803 INFO [org.hawkular.agent.monitor.scheduler.SchedulerService] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR010012: Starting scheduler
在 Grafana Web 控制台上，我使用此命令添加了 hawkular 插件
# grafana-cli plugins install hawkular-datasource
并且 hawkular 0.39 已成功附加到 Grafana web 控制台。
然而，当我使用 Hawkular 插件制作仪表板时，Hawkular 的任何指标都不会被带到 Grafana 服务器。
我是否错过了使用 Grafana 进行 Hawkular 监控的任何过程？
已更新
恐怕没有显示如下图所示的指标标题
但下图显示 http://192.168.200.51:8080/hawkular/metrics 站点给出了成功指标
有什么想法吗？现在我将我的Centos 7重新格式化并重新安装所有应用程序。
根据您的屏幕截图，您在数据源配置面板中为租户设置了 test。
尝试将其设置为 hawkular（Hawkular Wildfly 代理中的默认值），然后您应该会看到一些指标。
我的 OS 是 CentOS 7 和 运行 Wildfly 10.1。监控工具是Hawkular 0.39.0和Grafana server 3.1.1。我修改了Hawkular和Wildfly的具体IP。以下是日志内容
鹰派
18:19:01,601 INFO [org.hawkular.metrics.core.dropwizard.MetricsInitializer] (RxComputationScheduler-1) Finished creating metrics in 702 ms
18:19:01,721 WARN [com.datastax.driver.core.Cluster] (cluster2-worker-0) Re-preparing already prepared query is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once. Query='SELECT DISTINCT tenant_id, tname FROM metrics_tags_idx'
18:19:01,803 INFO [org.hawkular.metrics.core.util.GCGraceSecondsManager] (metricsservice-lifecycle-thread) Checking tables in hawkular_metrics to see if gc_grace_seconds needs to be updated
18:19:01,811 INFO [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle] (metricsservice-lifecycle-thread) HAWKMETRICS200005: Metrics service started
18:19:01,830 INFO [org.hawkular.metrics.core.util.GCGraceSecondsManager] (RxComputationScheduler-3) Finished gc_grace_seconds updates in 26 ms
18:19:02,081 INFO [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (Hawkular Java Agent Start Thread) HAWKMONITOR010039: The command-gateway URL is [ws://192.168.200.51:8080/hawkular/command-gateway/feed/localhost]
18:19:02,148 INFO [org.hawkular.agent.monitor.scheduler.SchedulerService] (Hawkular Java Agent Start Thread) HAWKMONITOR010012: Starting scheduler
18:19:02,148 INFO [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (OkHttp http://192.168.200.51:8080/...) HAWKMONITOR010034: Opened feed WebSocket connection to endpoint [ws://192.168.200.51:8080/hawkular/command-gateway/feed/localhost]
18:19:02,195 INFO [org.apache.activemq.artemis.ra] (default-threads - 4) AMQ151000: awaiting topic/queue creation HawkularQueue
18:19:02,200 INFO [org.hawkular.agent.monitor.protocol.ProtocolServices] (Hawkular Java Agent Start Thread) HAWKMONITOR010019: Managed server [Local DMR] is disabled. It will not be monitored.
18:19:02,228 INFO [org.apache.activemq.artemis.ra] (default-threads - 2) AMQ151000: awaiting topic/queue creation HawkularCommandEvent
18:19:02,239 INFO [org.hawkular.cmdgw.command.ws.server.FeedWebSocket] (default task-7) HAWKFEEDCOMM000013: WebSocket session [localhost] opened for endpoint [/feed/{feedId}]
18:19:02,328 INFO [org.xnio] (Hawkular Java Agent Start Thread) XNIO version 3.3.4.Final
野蝇 10.1
18:18:55,599 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 11438ms - Started 894 of 1172 services (470 services are lazy, passive or on-demand)
18:18:55,603 INFO [org.hawkular.agent.monitor.service.AgentCoreEngine] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR010084: Hawkular Agent: WildFly Agent Subsystem version 1.0.0.CR6
18:18:55,632 INFO [org.hawkular.agent.monitor.service.AgentCoreEngine] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR010000: Starting Hawkular Agent
18:18:55,632 INFO [org.hawkular.agent.monitor.service.MonitorService] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR020059: Agent is using storage adapter mode [HAWKULAR]
18:18:55,632 INFO [org.hawkular.agent.monitor.service.MonitorService] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR020050: Tenant ID [hawkular]
18:18:55,654 INFO [org.hawkular.agent.monitor.service.MonitorService] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR020025: Will talk to Hawkular at URL [http://192.168.200.51:8080]
18:19:06,777 INFO [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR010039: The command-gateway URL is [ws://192.168.200.51:8080/hawkular/command-gateway/feed/51491521-cdcb-4d11-9869-676b06491c8e]
18:19:06,793 INFO [org.hawkular.agent.monitor.cmd.FeedCommProcessor] (OkHttp http://192.168.200.51:8080/...) HAWKMONITOR010034: Opened feed WebSocket connection to endpoint [ws://192.168.200.51:8080/hawkular/command-gateway/feed/51491521-cdcb-4d11-9869-676b06491c8e]
18:19:06,803 INFO [org.hawkular.agent.monitor.scheduler.SchedulerService] (Hawkular WildFly Agent Startup Thread) HAWKMONITOR010012: Starting scheduler
在 Grafana Web 控制台上，我使用此命令添加了 hawkular 插件
# grafana-cli plugins install hawkular-datasource
并且 hawkular 0.39 已成功附加到 Grafana web 控制台。
然而，当我使用 Hawkular 插件制作仪表板时，Hawkular 的任何指标都不会被带到 Grafana 服务器。
我是否错过了使用 Grafana 进行 Hawkular 监控的任何过程？
已更新
恐怕没有显示如下图所示的指标标题
但下图显示 http://192.168.200.51:8080/hawkular/metrics 站点给出了成功指标
有什么想法吗？现在我将我的Centos 7重新格式化并重新安装所有应用程序。
根据您的屏幕截图，您在数据源配置面板中为租户设置了 test。
尝试将其设置为 hawkular（Hawkular Wildfly 代理中的默认值），然后您应该会看到一些指标。