加特林没有登录潮流?

时间:2017-01-11 09:26:47

标签: gatling influxdb

我已尝试按照http://gatling.io/docs/2.2.3/realtime_monitoring/index.html上的指南将测试结果记录到Influxdb并将数据显示在我之前设置的grafana中。但是我看不到gatling应该在Influxdb中的任何地方记录的任何数据。

我已经由Influxdb.conf文件编辑,因此它包含以下字段:

[[graphite]]
enabled = true
database = "gatlingdb"
bind-address = ":2003"
protocol = "tcp"
consistency-level = "one"
name-separator = "."


templates = [
  "gatling.*.*.*.count measurement.simulation.request.status.field",
  "gatling.*.*.*.min measurement.simulation.request.status.field",
  "gatling.*.*.*.max measurement.simulation.request.status.field",
  "gatling.*.*.*.percentiles50 measurement.simulation.request.status.field",
  "gatling.*.*.*.percentiles75 measurement.simulation.request.status.field",
  "gatling.*.*.*.percentiles95 measurement.simulation.request.status.field",
  "gatling.*.*.*.percentiles99 measurement.simulation.request.status.field"
]

和我的gatling.conf文件包含以下字段:

 data {
writers = [console, file, graphite]      # The list of DataWriters to which Gatling write simulation data (currently supported : console, file, graphite, jdbc)
console {
  #light = false                # When set to true, displays a light version without detailed request stats
}

graphite {
  #light = false              # only send the all* stats
  host = "127.0.0.1"         # The host where the Carbon server is located
  port = 2003                # The port to which the Carbon server listens to (2003 is default for plaintext, 2004 is default for pickle)
  protocol = "tcp"           # The protocol used to send data to Carbon (currently supported : "tcp", "udp")
  rootPathPrefix = "gatling" # The common prefix of all metrics sent to Graphite
  #bufferSize = 8192          # GraphiteDataWriter's internal data buffer size, in bytes
  #writeInterval = 1          # GraphiteDataWriter's write interval, in seconds
}

每当我运行我的gatling测试时,我看到没有错误消息或任何表明出现任何问题的信息,但我看不到潮流日志中有任何内容表明任何内容已记录到Influxdb,我也看不到任何数据gatlingdb数据库。我在Ubuntu上使用了Influxdb v0.10和gatling v2.2.3

任何人都可以帮我弄清楚我做错了吗?

1 个答案:

答案 0 :(得分:1)

已更新为Influxdb v1.1,问题似乎解决了这个问题