Electricitymap-contrib: Link to relevant logs when data is missing

[fbarl]

Inspired by @systemcatch's comment in https://github.com/tmrowco/electricitymap-contrib/issues/1977#issuecomment-580300670.

The current public Kibana logger seems like a great entry point for finding out why current data might be missing for some regions. We could add a sentence _"See the logs for more information"_ (filtering log messages by the selected region) to spread awareness about the logger and engage users more directly in debugging parsers.

[corradio]

Love that

On Thu, Feb 20, 2020 at 11:06 AM Filip Barl [e-mail]
wrote:

Inspired by @systemcatch https://github.com/systemcatch's comment in #1977
(comment)
https://github.com/tmrowco/electricitymap-contrib/issues/1977#issuecomment-580300670
.

The current public Kibana logger
@timestamp',asc))>
seems like a great entry point for finding out why current data might be
missing for some regions. We could add a sentence "See the logs
@timestamp',asc))>
for more information" to spread awareness about the logger and engage
users more directly in debugging parsers.

[image: image]
https://user-images.githubusercontent.com/1216874/74922332-52295e80-53cf-11ea-9598-2b97b9b2403f.png

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tmrowco/electricitymap-contrib/issues/2230?email_source=notifications&email_token=AAMUIKGACTFGHUNTXLBFVDTRDZIZNA5CNFSM4KYLM4KKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IO52U2A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMUIKGKG5PKE5Q6OOXEM3DRDZIZNANCNFSM4KYLM4KA
.

--

Olivier Corradi

Founder, CEO

https://www.linkedin.com/in/oliviercorradi https://twitter.com/corradio

tmrow.com

[systemcatch]

This would be great for getting more people involved in debugging and fault finding.

[corradio]

cc @sorensvejstrup and @martincollignon as inspiration and food for thought for our North app

[robertahunt]

I am not sure if this will work permanently, but at the moment it works for me to just change the last 'NL' to the zone_key in the following url:

https://kibana.electricitymap.org/app/kibana#/discover?_g=()&_a=(columns:!(_source),filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'96f67170-0c49-11e9-85c1-1d63df8c862c',key:level,negate:!f,params:(query:ERROR,type:phrase),type:phrase,value:ERROR),query:(match:(level:(query:ERROR,type:phrase)))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:'96f67170-0c49-11e9-85c1-1d63df8c862c',key:extra.key,negate:!f,params:(query:NL,type:phrase),type:phrase,value:NL),query:(match:(extra.key:(query:NL,type:phrase))))),index:'96f67170-0c49-11e9-85c1-1d63df8c862c',interval:auto,query:(language:lucene,query:''),sort:!('@timestamp',desc))

Could we do some javascript magic to replace 'NL' with the appropriate zone key when a data source is down?

[fbarl]

Could we do some javascript magic to replace 'NL' with the appropriate zone key when a data source is down?

Yup, that's exactly how I imagined it would work :)

[fbarl]

This issue was addressed by #2498.