{"action":"created","issue":{"url":"https://api.github.com/repos/amonapp/amon-issues/issues/22","repository_url":"https://api.github.com/repos/amonapp/amon-issues","labels_url":"https://api.github.com/repos/amonapp/amon-issues/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/amonapp/amon-issues/issues/22/comments","events_url":"https://api.github.com/repos/amonapp/amon-issues/issues/22/events","html_url":"https://github.com/amonapp/amon-issues/issues/22","id":155040893,"number":22,"title":"Each amonagent 'checkin' registering as unique server","user":{"login":"hailthemelody","id":6835016,"avatar_url":"https://avatars.githubusercontent.com/u/6835016?v=3","gravatar_id":"","url":"https://api.github.com/users/hailthemelody","html_url":"https://github.com/hailthemelody","followers_url":"https://api.github.com/users/hailthemelody/followers","following_url":"https://api.github.com/users/hailthemelody/following{/other_user}","gists_url":"https://api.github.com/users/hailthemelody/gists{/gist_id}","starred_url":"https://api.github.com/users/hailthemelody/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hailthemelody/subscriptions","organizations_url":"https://api.github.com/users/hailthemelody/orgs","repos_url":"https://api.github.com/users/hailthemelody/repos","events_url":"https://api.github.com/users/hailthemelody/events{/privacy}","received_events_url":"https://api.github.com/users/hailthemelody/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2016-05-16T14:27:50Z","updated_at":"2016-05-24T18:30:01Z","closed_at":null,"body":"Hi,\r\n\r\nIt appears that every 'checkin' from amonagent to the Amon service (I'm using Amon Personal currently to test it out) is registering as a unique server. I have experimented with fresh Amon Personal installs with and without SSL (changing the API keys on hosts running amonagent obviously), as well as with several different hosts running amonagent. Same result.\r\n\r\nI am running Amon Personal on Ubuntu 14.04, installed via the `bash -c \"$(curl -L https://www.amon.cx/install-personal/)\"` command provided via https://www.amon.cx/docs/personal/. The amonagent checks came in from Debian 7 and Ubuntu 14.04 hosts.\r\n\r\n![amon-personal](https://cloud.githubusercontent.com/assets/6835016/15292179/61357e30-1b71-11e6-9da7-c273909569f8.png)\r\n\r\n_The above screenshot is of a recent experiment with only one host, though as I mentioned above the same issue occurred with more than one host._"},"comment":{"url":"https://api.github.com/repos/amonapp/amon-issues/issues/comments/221361608","html_url":"https://github.com/amonapp/amon-issues/issues/22#issuecomment-221361608","issue_url":"https://api.github.com/repos/amonapp/amon-issues/issues/22","id":221361608,"user":{"login":"hailthemelody","id":6835016,"avatar_url":"https://avatars.githubusercontent.com/u/6835016?v=3","gravatar_id":"","url":"https://api.github.com/users/hailthemelody","html_url":"https://github.com/hailthemelody","followers_url":"https://api.github.com/users/hailthemelody/followers","following_url":"https://api.github.com/users/hailthemelody/following{/other_user}","gists_url":"https://api.github.com/users/hailthemelody/gists{/gist_id}","starred_url":"https://api.github.com/users/hailthemelody/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hailthemelody/subscriptions","organizations_url":"https://api.github.com/users/hailthemelody/orgs","repos_url":"https://api.github.com/users/hailthemelody/repos","events_url":"https://api.github.com/users/hailthemelody/events{/privacy}","received_events_url":"https://api.github.com/users/hailthemelody/received_events","type":"User","site_admin":false},"created_at":"2016-05-24T18:30:01Z","updated_at":"2016-05-24T18:30:01Z","body":"Further, default amonagent installs don't register with the Amon service unless I append `:80` in the `/etc/opt/amonagent/amonagent.conf` file.\r\n\r\nThe following _does not_ work, which is the default file that it created:\r\n```\r\n{\"api_key\": \"ABEPWqkKX7waIkApZ1hila0fFaGlb0czhrpdaxpHjbE\" , \"amon_instance\": \"http://192.168.2.43\"}\r\n```\r\n\r\nThe follow _does_ work, by adding the default port explicitly, which was not done by default:\r\n\r\n```\r\n{\"api_key\": \"ABEPWqkKX7waIkApZ1hila0fFaGlb0czhrpdaxpHjbE\" , \"amon_instance\": \"http://192.168.2.43:80\"}\r\n```\r\n\r\n\r\n I am using the default install instructions as provided by the service, using a stock install:\r\n\r\n```\r\nAPI_KEY=ABEPWqkKX7waIkApZ1hila0fFaGlb0czhrpdaxpHjbE bash -c \"$(curl -L http://192.168.2.43/install/)\r\n```\r\n"}}
{"actor":{"display_login":"hailthemelody"}}