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

Configuration Guide missing and a little mistake #19

Closed
Fiiti opened this issue Mar 8, 2017 · 5 comments
Closed

Configuration Guide missing and a little mistake #19

Fiiti opened this issue Mar 8, 2017 · 5 comments

Comments

@Fiiti
Copy link

Fiiti commented Mar 8, 2017

Hi Thomas,
I wonder, how I can read more about the configuration terms?
Like this fork

Also is it possible to use the storage-schemas.conf like the fork above? So I can use more time sections?


The lillte mistake in your Read.me:

Edit /etc/icingaweb2/modules/graphite/config.ini and set web\_url to the Graphite web host.

should read as web_url , didn't it?

BTW:
should the settings
[graphite] web_url = http://my.graphite.web
not written with the used port [graphite] web_url = http://my.graphite.web:2003 ?

Best regards,
Fiiti

@dnsmichi
Copy link
Contributor

dnsmichi commented Mar 8, 2017

FYI: That findmypast community module isn't a fork of this one, but actually a custom implementation based on the PNP module.

@Fiiti
Copy link
Author

Fiiti commented Mar 12, 2017

Ahh, okay- my failure. And what about the commands? Is there a guide anywhere?

@dgoetz
Copy link

dgoetz commented Mar 13, 2017

You can configure storage-schemas as you like, but keep in mind your check intervals for doing so.

And yes, you can add a port to the URL, but 2003 indicates you want to try to directly connect to graphite, but this module uses graphite web as interface, so typically port 80 or 443 which is default for http/https is fine.

@Fiiti
Copy link
Author

Fiiti commented Mar 13, 2017

Thanks.
BTW: I corrected in my first entry the mistake at web_url. It wasn't right shown, because i used BOLD Tags and the wrong backslash.

@Al2Klimov
Copy link
Member

@Fiiti Since 777204d the module may be configured over the web UI so you don't have to deal with any ini files or backslashes.

"should read as web_url , didn't it?" – No, because _ is part of the markdown syntax.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants