You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 6, 2022. It is now read-only.
It pulls 'raw' data fine, but if you try and apply an aggregator or a transformation:
(1) It selects BOTH if you choose either one, automatically, and they MUST be the same
(2) It does't work, anyways, with the javascript error:
this.datasource.convertToChronixInterval is not a function. (In 'this.datasource.convertToChronixInterval(this.target.horAggregator.samplingRate)', 'this.datasource.convertToChronixInterval' is undefined)
Tried both git clone, and then also building from src
building from src, had to change .contains to .includes, due to upstream changes in node libraries
The text was updated successfully, but these errors were encountered:
So the chronix.grafana plug-in is currently in WIP.
I talked to our javascript guy (he has lots on his plate) but we will try to make a beta release soon.
@devaudio do you actively use aggregations and/or transformations? chronix.grafana does not support it at all at this moment (and it was more of a bug that it showed up in the config screen after all...).
=> If you really want aggregations and/or transformations, let us know. Otherwise, I'd just remove the options from the config screen (for now).
heh i wanted to use them, because i have aggregation points with duplicate tags, but i won't throw a wrench into anything that gets it working smoothly for 4.X--- i'll suggest features after that is all finished
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It pulls 'raw' data fine, but if you try and apply an aggregator or a transformation:
(1) It selects BOTH if you choose either one, automatically, and they MUST be the same
(2) It does't work, anyways, with the javascript error:
Tried both git clone, and then also building from src
building from src, had to change .contains to .includes, due to upstream changes in node libraries
The text was updated successfully, but these errors were encountered: