{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/kibana/issues/3488","labels_url":"https://api.github.com/repos/elastic/kibana/issues/3488/labels{/name}","comments_url":"https://api.github.com/repos/elastic/kibana/issues/3488/comments","events_url":"https://api.github.com/repos/elastic/kibana/issues/3488/events","html_url":"https://github.com/elastic/kibana/issues/3488","id":65464797,"number":3488,"title":"Kibana 4: missing features from Kibana 3","user":{"login":"flopma","id":2256136,"avatar_url":"https://avatars.githubusercontent.com/u/2256136?v=3","gravatar_id":"","url":"https://api.github.com/users/flopma","html_url":"https://github.com/flopma","followers_url":"https://api.github.com/users/flopma/followers","following_url":"https://api.github.com/users/flopma/following{/other_user}","gists_url":"https://api.github.com/users/flopma/gists{/gist_id}","starred_url":"https://api.github.com/users/flopma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/flopma/subscriptions","organizations_url":"https://api.github.com/users/flopma/orgs","repos_url":"https://api.github.com/users/flopma/repos","events_url":"https://api.github.com/users/flopma/events{/privacy}","received_events_url":"https://api.github.com/users/flopma/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-03-31T14:27:45Z","updated_at":"2015-04-08T12:41:10Z","closed_at":"2015-03-31T14:53:19Z","body":"Hi,\r\n\r\nThank you for this software which is really powerful and useful.\r\n\r\nWe currently use Kibana 3 to help use understand what is triggering certain problems on the web applications we operates (the Atlassian stack - jira/confluence/bamboo/fisheye/...). The logs Apache HTTPD generates daily are enourmous and Kibana helps us.\r\n\r\nI just tried to replace Kibana 3 by Kibana 4 but the new interface does not permit easily to create dynamic multi-queries search with different colors, add markers. Kibana 3 is powerful in this. And digging the access_log of httpd with Kibana 3 like this is mostly useful because the multi-queries you use today maybe be different than the one tomorrow, etc... because the performance (or others) problems arising today in the application we monitor might be different the day after. Kibana 4 does not help in this (or am I just ignorant in its usage ?).\r\n\r\nAny information regarding the plans you have for the functionnality Kibana 3 provides ? Are you done with Kibana 3 - no more update (maybe it is mature enough?) ? Or will you integrate this functionnality in Kibana 4 ?\r\n\r\nThx a lot,\r\n\r\nIssa"},"comment":{"url":"https://api.github.com/repos/elastic/kibana/issues/comments/90902743","html_url":"https://github.com/elastic/kibana/issues/3488#issuecomment-90902743","issue_url":"https://api.github.com/repos/elastic/kibana/issues/3488","id":90902743,"user":{"login":"flopma","id":2256136,"avatar_url":"https://avatars.githubusercontent.com/u/2256136?v=3","gravatar_id":"","url":"https://api.github.com/users/flopma","html_url":"https://github.com/flopma","followers_url":"https://api.github.com/users/flopma/followers","following_url":"https://api.github.com/users/flopma/following{/other_user}","gists_url":"https://api.github.com/users/flopma/gists{/gist_id}","starred_url":"https://api.github.com/users/flopma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/flopma/subscriptions","organizations_url":"https://api.github.com/users/flopma/orgs","repos_url":"https://api.github.com/users/flopma/repos","events_url":"https://api.github.com/users/flopma/events{/privacy}","received_events_url":"https://api.github.com/users/flopma/received_events","type":"User","site_admin":false},"created_at":"2015-04-08T12:41:10Z","updated_at":"2015-04-08T12:41:10Z","body":"Well, we centralised all the Apache HTTPD access_log of 9 different\napplications which are part of a big solution for developers at our site\n(Atlassian Crowd, Jira, Confluence, Bamboo, Fisheye, Crucible, Nexus,\nSubversion, Stash). All apps interconnects and can communicate directly with\neach other (the Atlassian one). Also, we have plugins installed for some of\nthe apps which brings new functionnality but also possible troubles.\n\nSo when slowness appear, we never know what to look for initially.\n\nToday it might be 2 jira plugins running awfully bad;\nTomorrow, it might be Crowd being slow because some user send lots of REST\ncall through Confluence which might have an impact on Crowd, and Crowd being\nthe authnz application, this will slow all others.\n\nSo, having predefined dashboards is useless for those kind of usage. You can\nnever think about all the different interactions which might create problems;\nand even if you do, it would mean to create a lot of visualizations in Kibana\n4.\n\nWith Kibana 3, easy, you just make use of the multi query functionnality and\nthe histogram is updated accordingly, and the different colors helps corralate\ninteracting source of problems.\n\nReally, Kibana 4 seems geared for statistics gathering.\nAnd we prefer Kibana 3 for our work when it comes to look through the logs to\nfind out why a certain problem arised.\n\n"}}