corpglory / grafana-data-exporter Goto Github PK

Hi,

As we discussed, we would like to see a Single button solution from where we can make an Excel export of all the panels, graphs in our dashboards at once.

Kind regards,

janwillemca

Along with "Linux installation" and "Docker installation", lets add "Installation from source"

Currently when the user clicks Export this window appears:

Making calendars opened by default would be convinient, since the user has to open them manually anyway:

Currently it is possible to input backend url only with http:// prefix.
Also putting a / at the end on the url makes it invalid.

We should support more input variations from the user, such as (8000 being the desired port):

• http://localhost:8000
• 127.0.0.1:8000
• 8000
• http://127.0.0.1:8000/

from production. https://github.com/CorpGlory/grafana-data-exporter/wiki/Getting-Started-Linux , grafana-data-exporter-0.3.3

I run $ node dist/server.js and get error:

module.js:549
    throw err;
    ^

Error: Cannot find module 'lodash'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.P (/home/alex/grafana-data-exporter-0.3.3/dist/server.js:784:18)
    at __webpack_require__ (/home/alex/grafana-data-exporter-0.3.3/dist/server.js:638:30)
    at fn (/home/alex/grafana-data-exporter-0.3.3/dist/server.js:48:20)
    at Object.<anonymous> (/home/alex/grafana-data-exporter-0.3.3/dist/server.js:696:11)
    at __webpack_require__ (/home/alex/grafana-data-exporter-0.3.3/dist/server.js:638:30)
    at fn (/home/alex/grafana-data-exporter-0.3.3/dist/server.js:48:20)

We should create template dashboard to simplify installation process with:

• all configured panels
• template variable for backend url
• simple-json-datasource as dependency

And post here maybe?

Currently, use can't choose port to run exporter at
We should add it to config

We should make a check for existence of exporteddirectory.
If it doesn't exist - it should be created.

Now we have such fields in task-status json:
Time | User | Datasource | Measurement | Exported Rows | Progress | Download CSV | Status | Delete
Measurement is only influxdb-related field and should be removed
Also, datasource field is always empty now, should change the way it is filled

When I try to export my panel with InfluxDB datasource, I got this error from the grafana-data-exporter

C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:58892
this._queryParts = queryStr.split(INFLUX_QUERY_TIME_REGEX);
^

TypeError: Cannot read properties of undefined (reading 'split')
at new InfluxdbMetric (C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:58892:37)
at metricFactory (C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:58833:16)
at Metric.get metricQuery [as metricQuery] (C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:58855:33)
at Object. (C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:32426:32)
at Generator.next ()
at C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:32379:71
at new Promise ()
at __awaiter (C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:32375:12)
at Object.queryByMetric (C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:32413:12)
at Exporter. (C:\Users\user\Downloads\Nouveau dossier\grafana-data-exporter-0.5.1\dist\server.js:58678:64)

But no error with the panel

So I checked the server.js file and did a little debug, I found out that this :

js var queryStr = datasource.params.q;

So basicly here, this script try to get the param "q" from the datasource.params, but my datasource look like this
params: { db: 'dataclient', epoch: 'ms' }, type: 'influxdb', datasourceId: 3
The param "q" is missing, I didn't look further, if anyone has a solution to this problem I would appreciate !

Grafana v7.0.0
InfluxDB v1.8.3
Grafana-data-exporter-panel v0.5.1
Grafana-data-exporter v0.5.1

Return more info about task instead of just Task added

We would like an new feature where we can use nested SELECT statements to in our panels to export data from our MySQL databases

(node:9864) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'queries' of undefined
at PostgresMetric.getQuery (/home/karansgs/Documents/GRAFANA/grafana-data-exporter-0.3.6/dist/server.js:45898:44)
at Object. (/home/karansgs/Documents/GRAFANA/grafana-data-exporter-0.3.6/dist/server.js:28160:44)
at Generator.next ()
at /home/karansgs/Documents/GRAFANA/grafana-data-exporter-0.3.6/dist/server.js:28113:71
at new Promise ()
at __awaiter (/home/karansgs/Documents/GRAFANA/grafana-data-exporter-0.3.6/dist/server.js:28109:12)
at Object.queryByMetric (/home/karansgs/Documents/GRAFANA/grafana-data-exporter-0.3.6/dist/server.js:28147:12)
at Target. (/home/karansgs/Documents/GRAFANA/grafana-data-exporter-0.3.6/dist/server.js:45543:62)
at Generator.next ()
at /home/karansgs/Documents/GRAFANA/grafana-data-exporter-0.3.6/dist/server.js:45482:71
(node:9864) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)

Hi

I'm trying to get this plugin working on Grafana version 7.1.5 but if i click on the export button in the Export panel i receive an Unknown Error. Also grafana.log doesn't show any fault codes or errors. Is this plugin already tested on Grafana 7.1.5?

Kind Regards

JanwillemCA

We should create release after closing the most important tasks

P.S. don't forget to update changelog

Sometimes you need guaranty that your file has certain default format. So just time, value
Would have a way to get such csv

We should make app instead of panel with:

• panel
• simple-json-datasource (if possible)
• dashboard

this is what I get (node:9778) UnhandledPromiseRejectionWarning: Error: Please configure API key for http://localhost:3000

1. Client knows nothing about the error
2. we can show a link to a page with instruction how to this this problem

After CorpGlory/grafana-data-exporter-panel#6 progress is counted wrong, because it expects integral amount of days to export (from 00:00 of 1st day to 00:00 of 2nd day)
We should count progress differently

We have measurement as part of exported filename now
It's influxdb-only field, should use something not datasource-specific

Hi all,

as mentioned in the topic. I followed the installation instructions and are not able to export data.

Whenever I try to export data I get following error:

I am running Grafana v7.3.6 on Ubuntu Server 20.04.

Can anybody help me out? What am I doing wrong?

Cheers
Andre

Edit: The datasource I am trying to export data from is InfluxDB.

• use lib instead of code in src/grafana-datasource-kit
• pass apiKey from exporter to kit

I noticed the Grafana-data-exporter failing to pull the data, below are the details for the components I'm using.

Grafana-exporter-version: v0.5.1
Grafana-version: v7.1.5
datasource: Prometheus

Below is the error log grafana-data-exporter

0 day: 1611858600000ms -> 1611945000000ms
│ (node:25) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of undefined
│ at /var/www/dist/server.js:59057:44
│ at Array.map ()
│ at PrometheusMetric.getResults (/var/www/dist/server.js:59053:20)
│ at Object. (/var/www/dist/server.js:32429:44)
│ at Generator.next ()
│ at fulfilled (/var/www/dist/server.js:32376:58)
│ at runMicrotasks ()
│ at processTicksAndRejections (internal/process/task_queues.js:93:5) (node:25) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
(node:25) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I'm stuck, any help is appreciated.