Couldn't create report for search

reporting

#1

Hello,

I followed X-Pack reporting settings in Kibana | Kibana User Guide [6.5] | Elastic, yet while trying to generate report, I get following message:

"Couldn't create report for search 'test'"

Error: Failed to decrypt report job data.
Please ensure that xpack.reporting.encryptionKey is set and re-generate this report.

xpack.reporting.encryptionKey IS set:

sh-4.2$ export | egrep 'XPACK_REPORTING'
export XPACK_REPORTING_ENABLED="true"
export XPACK_REPORTING_ENCRYPTIONKEY="X"
sh-4.2$ 

Please advise.


(Tim Roes) #2

@tsullivan or @joelgriffith could one of you help out on this? Thanks.


(Joel Griffith) #3

@alexus do you happen to know if the instances share the same reporting index? We've found that if all kibana instances use different indexes there can be issues with how reporting works:

Multiple kibana.index settings across Kibana instances : if each instance a unique kibana.index setting but has the same xpack.reporting.index setting, it's possible that workers can claim a job that they aren't able to fulfill. The job will contain references to saved objects that the instance doesn't have in its own kibana.index .

  • Solution : With different kibana.index settings across Kibana instances connected to the same Elasticsearch cluster, you must also configure a different xpack.reporting.index setting per each unique kibana.index

This assumes you have a few instances running (which I'm not sure if you do). It'd also be good to see your other env variables just to know more about the environment itself.


(system) closed #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.