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

Getting a 301 #2

Open
sentient opened this issue Jul 20, 2015 · 3 comments
Open

Getting a 301 #2

sentient opened this issue Jul 20, 2015 · 3 comments

Comments

@sentient
Copy link

First time trying this module. Not 100% sure if I configured it right, or if the code is outdated.

Can somebody confirm this module still works?

It seems the Monitis API might have changed and that I am processing a 301 redirect?

Error parsing JSON: [SyntaxError: Unexpected token <]

<title>301 Moved Permanently</title>

301 Moved Permanently


nginx/1.2.1
@ShaunDwyer
Copy link

I'm having the same problem... did you end up finding a fix?

@sentient
Copy link
Author

The api url's indeed changed. But I stopped further pursuing because it creates too many custom counters at Monitis (what is not free)

@ShaunDwyer
Copy link

I ended up figuring out the URLs thing too... Of note as well (i could be doing something wrong) but this script appears to not work with Monitis now anyway.. I suspect more than just the API URL changed.

I didn't realise it didn't group things by 'host'... I agree with you, its not cost effective if the counters can't be grouped together into their relevant hosts. The first device I want to monitor is a UPS that has about 8 metrics, and then there will be plenty more from there...

What did you end up using to feed data into Monitis?

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

2 participants