{"action":"created","issue":{"url":"https://api.github.com/repos/dakrone/es-mode/issues/29","repository_url":"https://api.github.com/repos/dakrone/es-mode","labels_url":"https://api.github.com/repos/dakrone/es-mode/issues/29/labels{/name}","comments_url":"https://api.github.com/repos/dakrone/es-mode/issues/29/comments","events_url":"https://api.github.com/repos/dakrone/es-mode/issues/29/events","html_url":"https://github.com/dakrone/es-mode/issues/29","id":151490207,"number":29,"title":"Issues when getting started with `es-command-center`","user":{"login":"vedang","id":84510,"avatar_url":"https://avatars.githubusercontent.com/u/84510?v=3","gravatar_id":"","url":"https://api.github.com/users/vedang","html_url":"https://github.com/vedang","followers_url":"https://api.github.com/users/vedang/followers","following_url":"https://api.github.com/users/vedang/following{/other_user}","gists_url":"https://api.github.com/users/vedang/gists{/gist_id}","starred_url":"https://api.github.com/users/vedang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vedang/subscriptions","organizations_url":"https://api.github.com/users/vedang/orgs","repos_url":"https://api.github.com/users/vedang/repos","events_url":"https://api.github.com/users/vedang/events{/privacy}","received_events_url":"https://api.github.com/users/vedang/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-04-27T21:01:35Z","updated_at":"2016-04-27T21:50:29Z","closed_at":null,"body":"Hi @dakrone,\r\n\r\nI faced the following problems when trying to run the command center part of `es-mode`:\r\n\r\n1. `es-cc-endpoint` is not queried on the fly (unlike `es-endpoint-url`), so this breaks the overall experience of the mode.\r\n2. I'm running ES 1.7 inside vagrant/vbox on a Mac, and in my case, CPU percent is not nested at `:os :cpu_percent` or at `:os :cpu :percent`. A percentage value is nested at `:process :cpu :percent`. Due to this, the `:cpu` metric is set to `nil` and this breaks `es-cc--spark-v-for-metric` and `es-cc--spark-h-for-historical-metric`\r\n3. In `es-cc--spark-h-for-historical-metric`, `stats` is not a list but a single metric. Running `reverse` on this throws an error. \r\n\r\nI patched together code in order to see this working, attaching the patch to this issue. It isn't a fix at all, but will highlight the problem areas.\r\n\r\nAll in all, I love being able to run json queries directly from inside Emacs. I have a bunch of interesting queries that I use to inspect my ES cluster, and this lets me run them directly from my buffer. Thanks for `es-mode`!\r\n[es-cc.txt](https://github.com/dakrone/es-mode/files/239381/es-cc.txt)\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/dakrone/es-mode/issues/comments/215240695","html_url":"https://github.com/dakrone/es-mode/issues/29#issuecomment-215240695","issue_url":"https://api.github.com/repos/dakrone/es-mode/issues/29","id":215240695,"user":{"login":"dakrone","id":19060,"avatar_url":"https://avatars.githubusercontent.com/u/19060?v=3","gravatar_id":"","url":"https://api.github.com/users/dakrone","html_url":"https://github.com/dakrone","followers_url":"https://api.github.com/users/dakrone/followers","following_url":"https://api.github.com/users/dakrone/following{/other_user}","gists_url":"https://api.github.com/users/dakrone/gists{/gist_id}","starred_url":"https://api.github.com/users/dakrone/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dakrone/subscriptions","organizations_url":"https://api.github.com/users/dakrone/orgs","repos_url":"https://api.github.com/users/dakrone/repos","events_url":"https://api.github.com/users/dakrone/events{/privacy}","received_events_url":"https://api.github.com/users/dakrone/received_events","type":"User","site_admin":false},"created_at":"2016-04-27T21:50:29Z","updated_at":"2016-04-27T21:50:29Z","body":"@vedang okay, I pushed a commit that should add support for 1.7.x (I tested it locally), it should also fix the historical things, which was a result of not getting correct stats from Elasticsearch, give it a try and let me know if you run into any more problems!"}}