Integrate with Graphite #37
Comments
|
Graphite specifically would be nice, but there may be value in just making a more generic url creation tool that you can mask off the date/time. |
|
+1 |
16 similar comments
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 Please |
|
+1 |
4 similar comments
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 :] |
|
+1 |
|
So... i'm familiar with Graphite, but how would everyone envision its Curtis Ruck On Tue, Nov 19, 2013 at 12:23 PM, Torkel Ödegaard
|
|
Kibana is a dynamic dashboard web UI which pulls data from elasticsearch. There's no reason why you couldn't pull data from graphite as well ( graphite has a long history of dashboards wars ). That being said, I doubt that the elasticsearch team has any interest in adding addition sources of data to Kibana. So |
|
@cbarraford and how about the other way around? replacing graphite's whisper with elasticsearch backend... (haven't seen the code of graphite and don't know python, so I have no idea how hard could that be... :]) |
|
@blufor I like the idea. I dunno how viable it is (not terrible familiar with the internals of ES). I would think it would make graphite easier to horizontally scale. I do know it is slated within graphite to drop whisper files in a future release but I dunno what for. — On Thu, Nov 21, 2013 at 6:13 AM, blufor notifications@github.com wrote:
|
|
+1 |
3 similar comments
|
+1 |
|
+1 |
|
+1 |
|
For the foreseeable future, using grafana is the best way to accomplish this. |
|
+1 |
|
The problem with grafana is that it has the exact opposite problem kibana has: it only works with data from Graphite, not logstash. The whole point of this issue was to be able to perform analysis across both datasets in the same place. I think one alternative possibility to this would be to use elasticsearch + kibana instead of graphite: that way Kibana would have access to both metric and log data. On the other hand, I'm not sure whether or not that would be practical. Do you believe elasticsearch is capable of handling large volumes of raw metrics data being thrown at it? (E.g. CPU usage, disk space, network load, etc from 10-15 servers sampled at 1-minute intervals?) I know graphite can, but I am under the impression elasticsearch was never intended to handle that sort of constant stream of data. |
|
I think the most important issue is to be able to load Graphite Events. |
|
We use both kibana and grafana. It will be great if the capabilities between the two could be merged into a single dashboard. +1 from me. |
|
+1 |
|
Can see kibana 4.3 has plugin support enabled. Should be a quickie for the brave to hook on Grafana to render as visualisation. And in your dashboard alongside the primordial ones :) |
|
For anyone else hitting this thread, Grafana 2.5 now has support for ElasticSearch as a backend and you can mix data sources on a single graph, allowing you to plot ElasticSearch & Graphite data side-by-side. Works great! http://grafana.org/blog/2015/10/28/Grafana-2-5-Released.html |
…enamed `CollectorService` to `AgentService` Closes elastic#37
remove jshint configs
* create windows cmd wrapper * use windows cmd wrapper on browser tests * be explicit about the mocha command location * use windows cmd wrapper on server tests * use windows cmd wrapper on build default to using npm as well
* create windows cmd wrapper * use windows cmd wrapper on browser tests * be explicit about the mocha command location * use windows cmd wrapper on server tests * use windows cmd wrapper on build default to using npm as well
* create windows cmd wrapper * use windows cmd wrapper on browser tests * be explicit about the mocha command location * use windows cmd wrapper on server tests * use windows cmd wrapper on build default to using npm as well
…7683) * Add deprecation message to coordinate map and region map * clean up text * add default distro link and view in maps link * move url generation into onClick handler * create tile map layer descritor * set metrics and color and scaling * lazy load createTileMapLayerDescriptor * tslint fixes * tslint cleanup for OSS code * add region map deprecation message * tslint cleanup * consolidate logic into LegacyMapDeprecationMessage * fix jest test * fix tile-map and region_map in OSS distro * tslint fixes * assert urlGenerator exists * update message text * ensure legacy-ids get correctly evaluated (#37) * handle 6.x region map saved objects * turn off field meta * fix type Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Thomas Neirynck <thomas@elastic.co>
…astic#77683) * Add deprecation message to coordinate map and region map * clean up text * add default distro link and view in maps link * move url generation into onClick handler * create tile map layer descritor * set metrics and color and scaling * lazy load createTileMapLayerDescriptor * tslint fixes * tslint cleanup for OSS code * add region map deprecation message * tslint cleanup * consolidate logic into LegacyMapDeprecationMessage * fix jest test * fix tile-map and region_map in OSS distro * tslint fixes * assert urlGenerator exists * update message text * ensure legacy-ids get correctly evaluated (elastic#37) * handle 6.x region map saved objects * turn off field meta * fix type Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Thomas Neirynck <thomas@elastic.co>
…s. (#77683) (#78651) * Add deprecated message to tile_map and region_map visualizations. (#77683) * Add deprecation message to coordinate map and region map * clean up text * add default distro link and view in maps link * move url generation into onClick handler * create tile map layer descritor * set metrics and color and scaling * lazy load createTileMapLayerDescriptor * tslint fixes * tslint cleanup for OSS code * add region map deprecation message * tslint cleanup * consolidate logic into LegacyMapDeprecationMessage * fix jest test * fix tile-map and region_map in OSS distro * tslint fixes * assert urlGenerator exists * update message text * ensure legacy-ids get correctly evaluated (#37) * handle 6.x region map saved objects * turn off field meta * fix type Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Thomas Neirynck <thomas@elastic.co> # Conflicts: # src/plugins/visualizations/public/vis_types/base_vis_type.ts * fix eslint error
and others
Kibana is a fantastic dashboard tool, but not all of the data we want on a dashboard is available from Elasticsearch and lives in Graphite instead. It would be great if there was some sort of integration with Graphite, and even better if the integration was deeper, allowing the same no-code method of building dashboards that include both Graphite and Elasticsearch data.
The text was updated successfully, but these errors were encountered: