Maciej Brencz

Guys, thanks for the reports. Please run phantomas in really verbose mode and provide the full output here: ``` DEBUG=* phantomas https://github.com/macbre/phantomas --verbose --runs 5 ```

``` You need to run with a version of node that supports ES Modules in the VM API. See https://jestjs.io/docs/ecmascript-modules ```

Now that's interesting ... ``` $ npm t (...) Segmentation fault (core dumped) npm ERR! Test failed. See above for more details. ```

@gmetais, thanks for the links. I guess one would need to write an app-specific custom module to monitor single page application.

@matthiastosch, I assume you're using the latest version of phantomas. If so, please try running phantomas using PhantomJS 2.0 (`--engine=webkit2`).

Well, phantomas is not responsible for running "browser" JavaScript - it's PhantomJS that gives you incorrect values. You can give SlimerJS a try - `--engine=gecko`.

Let's try the following approach: ``` database: phantomas name: phantomas_ tags: metric=,url=,tag= fields: value=125.64 1434055562000000000 ``` - [push](https://docs.influxdata.com/influxdb/v0.12/guides/writing_data/) all metrics to the same timeserie (with `phantomas_` prefix) - add an...

@anlutro, what if we push all metrics as fields in a single measurement?

Point 1: makes sense. As for the second point: I'd rather not consider `Age` response header. phantomas reports the caching policies from the "server perspective". Including `Age` in the equation...

@gmetais, thanks for this improvements / new metrics ideas! > What I could do: Please, do go ahead :slightly_smiling_face: > Maybe this kind of image analysis could even be split...