I don't know why the TSVB suddenly don't work anymore only for "Count" Aggregation. it show "The request for this panel failed. Failed to compile inline script [count *1] using lang [expression]. " But when i use the other aggregation like "Average, Cardinality". it works perfectly.
Also for other visualization (Bar, Pie , Metrics). The "Count" function is ok, do any one of you face it before?
I can't replicate it so I will need more information. I see another series the 2xx, what is it about. Can you also share your Options and Panel options configuration? @huynhmytuan you are also using the 7.10 version of the stack?
Hi, having the same issue as well on 7.9. The error message I'm getting is: "Failed to compile inline script [count * 1] using lang [expression]"
. Interestingly there's also another error in Timelion which says: [timelion_vis] > Timelion request error: undefined Error: in cell #1: [search_phase_execution_exception]
Hello I have the same issue on a 7.7.0 managed by AWS
The issue arose a few days ago but I am not aware of any recent change of our managed Elasticsearch platform. Does this mean that partial updates of the platform may occur "underground" without being notified ?
The issue is now solved. Though I am still surprised to not have full control on TSVB visualization plugin updates on our AWS managed cluster. I would really appreciate having some insights to understand what was going on.
I know there was a big shift between AWS and Elastic stack, same as MongoDb did a few years before. I understand and still love Elastic community.
That said, in the current case, despite our cluster is managed by AWS it is still based on Elastic stack, not OpenSearch (v7.7.0). It seems also that the user who opened the case observed a "sudden" issue too and he didn't mention operating a AWS cluster. Actually I just want to know if there is a kind of dynamic update of plugins like TSVB whereas the whole Kibana version remain the same and if any how to prevent this.
Hi @vincentditlevinz Thanks for the details and sorry that you had the issue, I am sure it was frustrating.
It looks like we could never replicate the issue with the 7.10 version on Elastic Stack, Elastic Cloud nor just a Docker Image and did not seem to get much more info to help debug. With a quick look I did not see a bunch of these bugs reported from our users which I would expect as we have many TSVB users (including myself)... I suspect (not positive) these may be all related to what you encountered.
We can not really comment on how AWS Managed Service work, and again I am not trying to discount the the AWS service it is very popular it is just that we (Elastic) have no insight on what happens behind the scene and how it is run / operated. I would suggest opening a ticket with AWS Support perhaps they can shed some light.
From Elastic Cloud perspective we do not "Background Update" components / Kibana / plugins et... updates only occur user initiated.
The AWS ES code is a significant fork of the Elasticsearch / Kibana code going very far back much further than 7.7