Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors in log should be more explicit #2607

Closed
yellowmegaman opened this issue Mar 31, 2017 · 1 comment
Closed

Errors in log should be more explicit #2607

yellowmegaman opened this issue Mar 31, 2017 · 1 comment
Labels
bug unexpected problem or unintended behavior
Milestone

Comments

@yellowmegaman
Copy link

Bug report

I'm using telegraf to gather metrics from cassandra via jolokia. When some metric is no longer available ( cassandra version change), all i get - URL returned with status 404

Relevant telegraf.conf:

[[outputs.influxdb]]
  urls = ["http://influxdb.service:8086"]
  database = "telegraf_some"
  retention_policy = ""
  write_consistency = "any"
  timeout = "5s"
[[inputs.cassandra]]
  name_prefix = "some_"
  context = "/jolokia/read"
  servers = ["some:some@localhost:8778"]
  metrics  = [
    ...
    "/org.apache.cassandra.metrics:type=ReadRepair,name=Attempted",
    "/org.apache.cassandra.metrics:type=ReadRepair,name=RepairedBackground",
    "/org.apache.cassandra.metrics:type=ReadRepair,name=RepairedBlocking"
    ...

System info:

cassandra in docker container (1.13) on debian system (jessie)
Telegraf 1.2.1-1

Steps to reproduce:

  1. use config above
  2. telegraf --debug -config /tmp/tele.conf
  3. ReadRepair metrics are not available, and even in debug mode all i see is URL returned with status 404.

Expected behavior:

URL returned with status 404 - host:port/jolokia/link_that_failed

Actual behavior:

URL returned with status 404

Feature Request

Please make 404 error more explicit

Thanks a lot in advance!

@danielnelson danielnelson added the bug unexpected problem or unintended behavior label Mar 31, 2017
@danielnelson danielnelson added this to the 1.3.0 milestone Mar 31, 2017
@danielnelson danielnelson modified the milestones: 1.3.0, 1.4.0 Apr 20, 2017
@danielnelson
Copy link
Contributor

Will be included in 1.4 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants