Skip to content
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.

Metric Namespace Error while loading plugin snap-plugin-collector-psutil #31

Closed
amanRaina opened this issue Sep 9, 2016 · 2 comments
Closed

Comments

@amanRaina
Copy link

amanRaina commented Sep 9, 2016

I am getting the error while loading snap plugin snap-plugin-collector-psutil. The error is as below -
Error loading plugin:
Metric namespace /intel/psutil/net/ens513f1.226/errout contains not allowed characters. Avoid using punctuations [. , ; ? !], slashes [| \ /], carets [^], quotations [" ` '], brackets [( ) [ ] { }], spaces [ ]

My tasks file looks like below-


version: 1
schedule:
type: "simple"
interval: "1s"
max-failures: 10
workflow:
collect:
metrics:
/intel/psutil/*: {}
config:
/intel/mock:
name: "root"
password: "secret"
publish:
-
plugin_name: "influx"
config:
host: "10.19.226.68"
port: 8086
database: "test"
user: "root"
password: "P@ssw0rd"

The OS details are as below -
CentOS Linux release 7.2.1511 (Core)
Kernel -
3.10.0-327.28.3.el7.x86_64

Let me know how to resolve this error?

@amanRaina amanRaina changed the title Error while loading plugin snap-plugin-collector-psutil Mteric Namespace Error while loading plugin snap-plugin-collector-psutil Sep 9, 2016
@amanRaina amanRaina changed the title Mteric Namespace Error while loading plugin snap-plugin-collector-psutil Metric Namespace Error while loading plugin snap-plugin-collector-psutil Sep 9, 2016
@jcooklin jcooklin added the bug label Sep 14, 2016
@IRCody
Copy link

IRCody commented Oct 5, 2016

@amanRaina: This was an issue with Snap and not specific to this plugin. This behavior changed following this PR. This will be part of the next release.

Could you try testing against a version of snapd built from master and let us verify that this resolves your issue?

@IRCody
Copy link

IRCody commented Oct 11, 2016

@amanRaina: Since the behavior around that particular error has changed and the issue has been open for awhile I'm going to close this. Please respond if it's still an issue with @ircody in the message and I can re-open.

@IRCody IRCody closed this as completed Oct 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants