Following #43, that could be nice to provide an npm package to integrate this project easily in a frontend project.

According to creating-node-js-modules from npm documentation, creating a package seem to be simple.
The requirements are:

• Create a package.json file with a main entry
• Propose a js file that will load the wasm ... but maybe isn't a good idea and we should let people this "custom" task and just provide an empty main.js
• A TravisCI or whatever to recreate the package after each new version published.

'test' 'name' STORE
''
<'
create(series(name))
'>
TSL

Fails

Current behaviour:

Make a TSL query a bad token, the response code will be 200 but the body says (in HTML): ...bad token..

Expected: TSL should return an errored status code (500 / 418 / ...)

• select("series").where("var=${varname}").from(start, to=end)
  is failing when varname is a number

I'm just asking, is this noteworthy project still being maintained? Thanks a lot.

Missing percentiles and join aggregators

This is more a question rather than an issue.

I have seen in the roadmap that an implementation independent from the back-end is foreseen. Has an implementation on top of python pandas been considered? Would it make senses according to you?

Thanks in anticipation for your response.

Error with Native variable
They can't be interpreted with ${} in TSL script in Grafana

When I draw a graph with the result of a TSL query, I often need to add a custom series which can be for example an upper limit.

Is it possible to do it in TSL to perform the two operations at the same time

Exemple:

create(series('metrics.service.mads').setLabels('service=abcd').addValue(now, 150).addValue(now - 1h, 150)...) 

It seems the ANTLR grammar file is not used by the project which instead uses a handcrafted parser, as a consequence, the grammar file does not seem to be updated whenever the features of the language evolve thus preventing implementations which rely on the ANTLR4 grammar to be up to date.

As an example, functions such as fill and fillValue are not present in the ANTLR files.

Are there any plans to actually use the grammar file for the go implementation so it would be kept up to date?

TSL already have .renameBy() function which allow us to rename a series with its labels.

For some use case, it could be interesting have template the name with a very custom string.

Can we extend .renameBy() function with the following behaviour ?

select('os.cpu').renameBy('${this.labels.hostname} (${this.labels.datacenter})' )
// produce a series named: "1.server.front (GRA)"

When using a
.from(start, to=end).sampleBy(1m, mean)
is failing

Hello,

when I get mutiple series, I cannot predict how the list of series will be sorted. I would like to be able to sort the list of series based on the name or a label of the series.
This way I am sure series will always be displayed in the same order in Grafana.

Thank you,
Tristan

curl -d "select('requests_latency_seconds_count').where('role=0').from('2019-01-31T00:00:00+01:00',to='2019-02-01T00:00:00+01:00').finite().sampleBy(1h,last).group(sum).window(delta, 0, 1)" https://DESC:[email protected]/v0/query

{"error":"Cannot parsed query: Error when parsing "to" in "from" function, this variable isn't declared at line 1, char 91"}

quick fix resolution (removing the to= instruction) see below:
curl -d "select('requests_latency_seconds_count').where('role=0').from('2019-01-31T00:00:00+01:00', '2019-02-01T00:00:00+01:00').finite().sampleBy(1h,last).group(sum).window(delta, 0, 1)" https://DESC:[email protected]/v0/query

I'd like to be able to set a new label from series names so I can use it in the query (for example with groupBy)

Example :

select(my.awesome.series.name.*.count)
  .where(...)
  .setLabelFromName("verb")
  .groupBy(verb, mean)

select(my.awesome.series.name.*.count)
  .where(...)
  .extractLabelFromName("verb","~MyRegex")
  .groupBy(verb, mean)

While executing this query on Quantum :

$RTOKEN 
<' 
select(*) 
'>
TSL

I encountered this error :

ERROR line #9: Exception at '=>TSL<=' in section [TOP] (Line #4 (Exception at '[ 'token' =>~.*<= {} ] FIND' in section [TOP] (Unknown function '~.*')))

This should work as indicated here : https://github.com/ovh/tsl/blob/master/spec/doc.md#select