| To: | Marko Myllynen <myllynen@xxxxxxxxxx> |
|---|---|
| Subject: | Re: pcp+graphite, take 2 |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Mon, 23 Jun 2014 14:04:36 -0400 |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <53A869FF.8080703@xxxxxxxxxx> |
| References: | <20140616214301.GB6693@xxxxxxxxxx> <53A181C4.5050402@xxxxxxxxxx> <y0mfvj2wf35.fsf@xxxxxxxx> <53A869FF.8080703@xxxxxxxxxx> |
| User-agent: | Mutt/1.4.2.2i |
Hi, Marko - > [...] > > Another possible change would be to have a less impressive > > default.json dashboard in other ways, maybe cutting down from two > > graphs to one, or restricting it to a smaller timeframe, or something > > like that. > [...] Did you try to share Grafana dashboards with others by > providing a URL? The "Share temp copy" didn't quite work for me and (Will look into it; might need to remove the related web buttons. Grafana & graphite appear covetous of fileservers like elasticsearch to store such stuff.) > a JSON file from "Export dashboard" is not very practical. One possibility is to do an export-dashboard, and plop the resulting .json file under the jsdemos/grafana/app/dashboards directory. That enables a custom URL with no action from the reader: see how the current jsdemos/index.html file selects between .../default.json and .../default-png.json. - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: pcp+graphite, take 2, Marko Myllynen |
|---|---|
| Next by Date: | RFC - pmie "ruleset" extension, Ken McDonell |
| Previous by Thread: | Re: pcp+graphite, take 2, Marko Myllynen |
| Next by Thread: | Re: pcp+graphite, take 2, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |