chaoss / grimoirelab-kibiter Goto Github PK
View Code? Open in Web Editor NEWThis project forked from elastic/kibana
Soft fork of Kibana, for the benefit of GrimoireLab
Home Page: https://chaoss.github.io/grimoirelab
License: Other
This project forked from elastic/kibana
Soft fork of Kibana, for the benefit of GrimoireLab
Home Page: https://chaoss.github.io/grimoirelab
License: Other
We're using Kibiter 6.1.4 from Bitergia and we've found out that when using bar charts there is an "Others" bucket that is automatically added as an existing bucket to the chart.
@alpgarcia tells us:
unfortunately Others feature is hardcoded into Kibiter. Each query with a size limit will show Others entry aggregating the rest of the documents that matches the query but are not within the selected size. In your case you are showing 25 milestones, so Others appears grouping the rest together.
It seems that this is a feature exclusive to Kibiter and not present at Kibana upstream. If it's needed for Kibiter, it would be nice to make it an opt-in feature (e.g. with a checkbox under Buckets options: "[x] Show others")
For more context:
SearchGuard, the security plugin we are currently using to manage the access to the Dashboard, doesn't allow to create short URLs to non-logged users. The reason is this requires writing access to .kibana
index.
This feature is interesting for some users, so they can share specific views of the data. A workaround is using an third-party service to shorten URL.
A possible solution could be using an external database to store short URLs with a single public API end-point to add a new one (same as other services do).
Kibiter is using Kibana 6.1.0. The latest version is 6.1.4. This update will close some bugs and add some important features as the Kibana API for saving objects.
Login buttons are expected to be on the top right.
Feature request: Include on the top right a menu item that says "Login"
That would significantly improve a new-user's experience.
Optional "awesome" extra: the button changes to "Logout" for logged-in users.
Kibana version:
Kibana 6.8.6 (the one currently used for biterg.io instances)
Elasticsearch version:
N/A
Server OS version:
N/A
Browser version:
Firefox 91.12.0esr (64-bit)
Browser OS version:
Linux 64-bit
Original install method (e.g. download page, yum, from source, etc.):
Debian package
Description of the problem including expected versus actual behavior:
When creating a network graph with different node sizes, they all are the same size as soon as you add a Relation.
Steps to reproduce:
github2_pull_requests
Errors in browser console (if relevant):
N/A
Provide logs and/or server output (if relevant):
N/A
Since this is a fork of Kibana, it's using its same README.md file, that could make sense. But there seems to be some differences about how it is run, specially as a container. And, since the README.md file is used in DockerHub as reference, that information is lost:
https://hub.docker.com/r/bitergia/kibiter/
For example, the environment variables meaning is missed. Things like PROJECT_NAME
, what do they mean?
Kibana version:6.1.0
Elasticsearch version:6.1.0
Server OS version:Ubuntu 16.04
Browser version:Firefox
Browser OS version:Ubuntu 16.04
Original install method (e.g. download page, yum, from source, etc.):download page
Description of the problem including expected versus actual behavior:
Expected: Kibana and Elasticsearch( Both Same Versions) to run without any issues
Actual:
log [04:32:22.507] [warning] You're running Kibana 6.1.0-1 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v6.1.0 @ 127.0.0.1:9200 (127.0.0.1)
Steps to reproduce:
Errors in browser console (if relevant): Unable to save when dashboard is up and running
Provide logs and/or server output (if relevant):
Describe the feature:
@GeorgLink found an error on the dashboard https://chaoss.biterg.io. The bug affects the legend of the heatmap, which is not correctly refreshed.
This is how you can reproduce it:
Kibana version: 5.1.1
Elasticsearch version: 5.1.1
Server OS version: NA
Browser version: Chromium 60.0.3112.78
Browser OS version: NA
Original install method (e.g. download page, yum, from source, etc.): NA
Description of the problem including expected versus actual behavior: Kibiter does not server any content but an Internal Server Error
Steps to reproduce:
Provide logs and/or server output (if relevant):
{
"type":"error",
"@timestamp":"2017-11-15T13:13:41Z",
"tags":[
],
"pid":1,
"level":"error",
"message":"/opt/kibana/src/ui/views/chrome.jade:12\n 10| meta(http-equiv='X-UA-Compatible', content='IE=edge,chrome=1')\n 11| meta(name='viewport', content='width=device-width')\n > 12| meta(name='description', content='Bitergia analytics for 'Mozilla' provided by Bitergia using GrimoireLab Open Source technology')\n 13| title Bitergia Analytics\n 14| style.\n 15| @font-face {\n\nUnexpected identifier",
"error":{
"message":"/opt/kibana/src/ui/views/chrome.jade:12\n 10| meta(http-equiv='X-UA-Compatible', content='IE=edge,chrome=1')\n 11| meta(name='viewport', content='width=device-width')\n > 12| meta(name='description', content='Bitergia analytics for 'Mozilla' provided by Bitergia using GrimoireLab Open Source technology')\n 13| title Bitergia Analytics\n 14| style.\n 15| @font-face {\n\nUnexpected identifier",
"name":"SyntaxError",
"stack":"SyntaxError: /opt/kibana/src/ui/views/chrome.jade:12\n 10| meta(http-equiv='X-UA-Compatible', content='IE=edge,chrome=1')\n 11| meta(name='viewport', content='width=device-width')\n > 12| meta(name='description', content='Bitergia analytics for 'Mozilla' provided by Bitergia using GrimoireLab Open Source technology')\n 13| title Bitergia Analytics\n 14| style.\n 15| @font-face {\n\nUnexpected identifier\n at assertExpression (/opt/kibana/node_modules/jade/lib/lexer.js:30:3)\n at Object.attrs (/opt/kibana/node_modules/jade/lib/lexer.js:676:20)\n at Object.next (/opt/kibana/node_modules/jade/lib/lexer.js:939:15)\n at Object.lookahead (/opt/kibana/node_modules/jade/lib/lexer.js:113:46)\n at Parser.lookahead (/opt/kibana/node_modules/jade/lib/parser.js:102:23)\n at Parser.peek (/opt/kibana/node_modules/jade/lib/parser.js:79:17)\n at Parser.tag (/opt/kibana/node_modules/jade/lib/parser.js:773:22)\n at Parser.parseTag (/opt/kibana/node_modules/jade/lib/parser.js:759:17)\n at Parser.parseExpr (/opt/kibana/node_modules/jade/lib/parser.js:211:21)\n at Parser.block (/opt/kibana/node_modules/jade/lib/parser.js:729:25)\n at Parser.tag (/opt/kibana/node_modules/jade/lib/parser.js:838:24)\n at Parser.parseTag (/opt/kibana/node_modules/jade/lib/parser.js:759:17)\n at Parser.parseExpr (/opt/kibana/node_modules/jade/lib/parser.js:211:21)\n at Parser.block (/opt/kibana/node_modules/jade/lib/parser.js:729:25)\n at Parser.tag (/opt/kibana/node_modules/jade/lib/parser.js:838:24)\n at Parser.parseTag (/opt/kibana/node_modules/jade/lib/parser.js:759:17)"
},
"url":{
"protocol":null,
"slashes":null,
"auth":null,
"host":null,
"port":null,
"hostname":null,
"hash":null,
"search":"",
"query":{
},
"pathname":"/app/kibana",
"path":"/app/kibana",
"href":"/app/kibana"
}
}
This issue is to activate protobot/dco (or similar bot) to check that all commits have a sign-off in this repository.
The CHAOSS Project Charter section 8.2.1 requires that all contributions are signed-off. The CHAOSS project has been piloting the use of DCO sign-offs. Once contributors know how to do it, sign-offs are easy to do with little overhead.
For users of the git command line interface, a sign-off is accomplished with the
-s
as part of the commit command:git commit -s -m 'This is a commit message'
For users of the GitHub interface, a sign-off is accomplished by writing
Signed-off-by: Your Name <[email protected]>
into the commit comment field. This can be automated by using a browser plugin like scottrigby/dco-gh-ui
To-Do for repo maintainers: Please inform your contributors about DCO sign-offs and comment on this issue when your are ready for the DCO bot to be activated on this repository.
Kibiter version: 6.1.4-1
Browser: Chrome 78.0.3904.97 (Build oficial) (64 bits)
Related (somehow) to: #107
Others
bucket is showing the number of documents that aren't included in any bucket. That makes the percentage to be wrong when using unique count
as metric, as Others
doesn't apply any metric but just a simple document count.
Steps to reproduce:
Some screenshots of this behavior (steps 4 and 6 respectively):
Kibiter is using Kibana 6.8.6. The latest version is 7.10.1 This update will add some important features as the Kibana API for saved query.
Kibana version:
kibiter-6.1.4-4-linux-x86_64
Elasticsearch version:
elasticsearch-7.6.0
Server OS version:
elementary OS Hera 5.1 based on on Ubuntu 18.04
Browser version:
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
tar -xzf
Description of the problem including expected versus actual behavior:
Trying to run kibiter gives syntax error
Steps to reproduce:
Errors in browser console (if relevant):
~/kibiter-6.1.4-4-linux-x86_64$ ./bin/kibana
/home/abid/kibiter-6.1.4-4-linux-x86_64/src/utils/streams/reduce_stream.js:40
async transform(chunk, enc, callback) {
^^^^^^^^^
SyntaxError: Unexpected identifier
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:542:28)
at Module._extensions..js (module.js:579:10)
at Object.require.extensions.(anonymous function) [as .js] (/home/abid/kibiter-6.1.4-4-linux-x86_64/node_modules/babel-register/lib/node.js:152:7)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
Provide logs and/or server output (if relevant):
Create a new Kibiter 5.6+ES 5.6 with ROR plugin active
(acs@dellx) ~ $ docker-compose -f ~/devel/GrimoireELK/docker/compose/bidek-56-lite.yml up -d
Add some data to the ES:
(acs@dellx) (master *$% u=) ~/devel/GrimoireELK/utils $ ./p2o.py -g -e http://bitergia:bitergia@localhost:9200 --enrich --index git git https://github.com/grimoirelab/perceval
Go to Kibiter at: http://localhost:5601 and try to create an index pattern for git_enrich. It will show you an Internal server error in the web page. The error in the web page is not useful at all, but taking a look to kibana logs:
(acs@dellx) (master *$% u=) ~/devel/GrimoireELK/utils $ docker logs --tail 10 -f compose_kibiter_1
{"type":"response","@timestamp":"2017-09-27T15:23:04Z","tags":[],"pid":1,"method":"get","statusCode":404,"req":{"url":"/api/index_patterns/_fields_for_wildcard?pattern=git_en&meta_fields=_source&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score","method":"get","headers":{"host":"localhost:5601","connection":"keep-alive","accept":"application/json, text/plain, */*","kbn-version":"5.6.0-SNAPSHOT","user-agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/61.0.3163.79 Chrome/61.0.3163.79 Safari/537.36","referer":"http://localhost:5601/app/kibana","accept-encoding":"gzip, deflate, br","accept-language":"es,en-US;q=0.8,en;q=0.6"},"remoteAddress":"172.17.0.1","userAgent":"172.17.0.1","referer":"http://localhost:5601/app/kibana"},"res":{"statusCode":404,"responseTime":11,"contentLength":9},"message":"GET /api/index_patterns/_fields_for_wildcard?pattern=git_en&meta_fields=_source&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score 404 11ms - 9.0B"}
{"type":"response","@timestamp":"2017-09-27T15:23:05Z","tags":[],"pid":1,"method":"get","statusCode":404,"req":{"url":"/api/index_patterns/_fields_for_wildcard?pattern=git_enri&meta_fields=_source&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score","method":"get","headers":{"host":"localhost:5601","connection":"keep-alive","accept":"application/json, text/plain, */*","kbn-version":"5.6.0-SNAPSHOT","user-agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/61.0.3163.79 Chrome/61.0.3163.79 Safari/537.36","referer":"http://localhost:5601/app/kibana","accept-encoding":"gzip, deflate, br","accept-language":"es,en-US;q=0.8,en;q=0.6"},"remoteAddress":"172.17.0.1","userAgent":"172.17.0.1","referer":"http://localhost:5601/app/kibana"},"res":{"statusCode":404,"responseTime":11,"contentLength":9},"message":"GET /api/index_patterns/_fields_for_wildcard?pattern=git_enri&meta_fields=_source&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score 404 11ms - 9.0B"}
{"type":"error","@timestamp":"2017-09-27T15:23:06Z","tags":[],"pid":1,"level":"error","message":"Cannot provide statusCode or message with boom error","error":{"message":"Cannot provide statusCode or message with boom error","name":"Error","stack":"Error: Cannot provide statusCode or message with boom error\n at Object.exports.assert (/opt/kibana/node_modules/hoek/lib/index.js:736:11)\n at Object.exports.wrap (/opt/kibana/node_modules/boom/lib/index.js:96:10)\n at convertEsError (/opt/kibana/src/server/index_patterns/service/lib/errors.js:67:25)\n at /opt/kibana/src/server/index_patterns/service/lib/es_api.js:63:40\n at throw (native)\n at step (/opt/kibana/src/server/index_patterns/service/lib/es_api.js:74:191)\n at /opt/kibana/src/server/index_patterns/service/lib/es_api.js:74:402"},"url":{"protocol":null,"slashes":null,"auth":null,"host":null,"port":null,"hostname":null,"hash":null,"search":"?pattern=git_enrich&meta_fields=%5B%22_source%22%2C%22_id%22%2C%22_type%22%2C%22_index%22%2C%22_score%22%5D","query":{"pattern":"git_enrich","meta_fields":"[\"_source\",\"_id\",\"_type\",\"_index\",\"_score\"]"},"pathname":"/api/index_patterns/_fields_for_wildcard","path":"/api/index_patterns/_fields_for_wildcard?pattern=git_enrich&meta_fields=%5B%22_source%22%2C%22_id%22%2C%22_type%22%2C%22_index%22%2C%22_score%22%5D","href":"/api/index_patterns/_fields_for_wildcard?pattern=git_enrich&meta_fields=%5B%22_source%22%2C%22_id%22%2C%22_type%22%2C%22_index%22%2C%22_score%22%5D"}}
{"type":"response","@timestamp":"2017-09-27T15:23:06Z","tags":[],"pid":1,"method":"get","statusCode":500,"req":{"url":"/api/index_patterns/_fields_for_wildcard?pattern=git_enrich&meta_fields=_source&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score","method":"get","headers":{"host":"localhost:5601","connection":"keep-alive","accept":"application/json, text/plain, */*","kbn-version":"5.6.0-SNAPSHOT","user-agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/61.0.3163.79 Chrome/61.0.3163.79 Safari/537.36","referer":"http://localhost:5601/app/kibana","accept-encoding":"gzip, deflate, br","accept-language":"es,en-US;q=0.8,en;q=0.6"},"remoteAddress":"172.17.0.1","userAgent":"172.17.0.1","referer":"http://localhost:5601/app/kibana"},"res":{"statusCode":500,"responseTime":16,"contentLength":9},"message":"GET /api/index_patterns/_fields_for_wildcard?pattern=git_enrich&meta_fields=_source&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score 500 16ms - 9.0B"}
Some queries are getting a 404 (forbidden from Kibana server), and finally a 500 code is returned.
Creating an index pattern for the git raw index works smoothly. The logs are:
{"type":"response","@timestamp":"2017-09-27T15:26:19Z","tags":[],"pid":1,"method":"get","statusCode":200,"req":{"url":"/api/index_patterns/_fields_for_wildcard?pattern=git&meta_fields=_source&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score","method":"get","headers":{"host":"localhost:5601","connection":"keep-alive","accept":"application/json, text/plain, */*","kbn-version":"5.6.0-SNAPSHOT","user-agent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/61.0.3163.79 Chrome/61.0.3163.79 Safari/537.36","referer":"http://localhost:5601/app/kibana","accept-encoding":"gzip, deflate, br","accept-language":"es,en-US;q=0.8,en;q=0.6"},"remoteAddress":"172.17.0.1","userAgent":"172.17.0.1","referer":"http://localhost:5601/app/kibana"},"res":{"statusCode":200,"responseTime":16,"contentLength":9},"message":"GET /api/index_patterns/_fields_for_wildcard?pattern=git&meta_fields=_source&meta_fields=_id&meta_fields=_type&meta_fields=_index&meta_fields=_score 200 16ms - 9.0B"}
Kibana version: 6.1.0
Elasticsearch version: 6.1.0
Server OS version: Ubuntu 16.04
Browser version: Firefox
Browser OS version: Ubuntu 16.04
Original install method (e.g. download page, yum, from source, etc.): source
Description of the problem including expected versus actual behavior:
Expected: Dashboard to save successfully after changes
Actual: Dashboard produces an error when trying to save changes
Steps to reproduce:
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Describe the feature:
The recent commit that adds KIBANA_DEFAULTAPPID breaks the container when the variable contains ' /'. The scenario of adding that char is pretty common as it is the way to redirect to an specific dashboard.
Kibana version:
Version: 6.1.4-1
Browser version:
Chrome
Browser OS version:
77.0.3865.90 (Official Build) (64-bit)
Original install method (e.g. download page, yum, from source, etc.):
Installed GrimoireLab via Docker using the Mac install instructions.
Description of the problem including expected versus actual behavior:
When there is a menu item with only one item (in my case, Slack and Discourse), the sub-menu items do not appear on the first activation of the menu. I have to hover over one of the other menu items (e.g. git, github) and activate the sub-menu before I can see the link to the overview link.
Steps to reproduce:
See screen cast here: https://youtu.be/24wTj7SaqdM where I'm demonstrating it a couple of times.
Since Elasticsearch 6.6.0 the setting elasticsearch.url
is replaced by elasticsearch.hosts
.
https://www.elastic.co/guide/en/kibana/6.8/settings.html
The README still shows ELASTICSEARCH_URL
has to be configured.
I think Kibiter should follow the settings like in original Kibana.
Seems ELASTICSEARCH_HOSTS
is currently not handled.
This means you also can't loadbalance on multiple elasticsearch nodes.
Furthermore I tried using a Traefik setup to loadbalance, but this still mandates me to run on port 9200. Preferably I would like to run my Loadbalancer on port 80 and 443 only.
The bug below affects the docker image: bitergia/kibiter:secured-v6.8.6-1
Kibana 6.8.6 uses a new parameter to declare the endpoints where the ES cluster is bind. This is named elasticsearch.hosts
. The Docker container is using the same variable we used in 6.1 to map an endpoint to that new parameter. This is nice because we don't need to think about the new variables but it is not correctly done. One of the goodies of this new parameter is that is allows an array of nodes.
The env variable available for Kibana 6.8.6 is the one below, have a look at the array.
ELASTICSEARCH_HOSTS='["http://10.45.3.2:9220","http://10.45.3.1:9230"]'
In our code we are just waiting for a single endpoint, which is reducing the new features provided by Kibana and affecting some of the customer of Bitergia as we need to use it.
Change the language to chinese, but it does not take effect.
Kibana version:
v6.8.6-3
Elasticsearch version:
v6.8.6
Server OS version:
mac os 10.15.5
Browser version:
chrome 84.0.4147.105
Browser OS version:
mac os 10.15.5
Original install method (e.g. download page, yum, from source, etc.):
git clone https://github.com/chaoss/grimoirelab.git
run the project with docker-compose
Description of the problem including expected versus actual behavior:
when I change the language through kibana browser setting:
or change the language in kibana.yml
:
when I restart the kibiter docker, the language of the browser is still english, but what i expect is chinese.
Steps to reproduce:
We want to build ZIP's for each Kibiter version. This could be usefull in order to check new versions or little changes.
Kibana has by default a way to build a tar.gz of the current version that you are, doing:
npm run build
This must create the tars into KIBITER_HOME/target/
, one tar for each OS. However, this command generates an error and it's impossible to continue, so we just add this option in order to avoid that error:
npm run build -- --skip-os-packages
Now, tars have been built and are in KIBITER_HOME/target/
.
Important: That command don't copy the plugins don't into the plugins/
folder of the tars, so it's needed to add this line into a grunt configurations file (before the tar creation):
KIBITER_HOME/tasks/build/archives.js
:async function archives({ name, buildName, zipPath, tarPath }) {
...
await exec('cp', ['-rf', fromRoot("plugins/"), fromRoot("build/" + buildName + "/.")]); //This line
await exec('tar', tarArguments);
}
The matrix here looks pretty out of date.
I note that ES 6.8 seems a viable option from the sample docker-compose.yml.
Not sure what the certification process was, but I'm happy to edit that wiki if that's the preferred approach.
When the kibiter container restarts following error occurs. The only solution to resolve it for now is to throw away the kibana_1 and kibana_2 indexes and restart it again.
Then to populate the dashboards I'm also restarting the grimoirelab:installed container so it recreates the dashboards.
Versions
See below what happens on a container restart, Just before it fails.
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["status","plugin:[email protected]","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["status","plugin:[email protected]","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["status","plugin:[email protected]","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["status","plugin:[email protected]","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["status","plugin:[email protected]","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["status","plugin:[email protected]","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["status","plugin:[email protected]","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["status","plugin:[email protected]","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:58Z","tags":["info","migrations"],"pid":1,"message":"Creating index .kibana_2."}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:36:59Z","tags":["info","migrations"],"pid":1,"message":"Migrating .kibana_1 saved objects to .kibana_2"}
kibiter_1 | {"type":"log","@timestamp":"2020-06-24T06:37:00Z","tags":["fatal","root"],"pid":1,"message":"{ Error: mapping set to strict, dynamic introduction of [release_date] within [dashboard] is not allowed\n at Object.write (/opt/kibana/src/server/saved_objects/migrations/core/elastic_index.js:110:23)\n detail:\n { index:\n { _index: '.kibana_2',\n _type: 'doc',\n _id: 'dashboard:Overview',\n status: 400,\n error: [Object] } } }"}
kibiter_1 |
kibiter_1 | FATAL Error: mapping set to strict, dynamic introduction of [release_date] within [dashboard] is not allowed
kibiter_1 |
code-chars_kibiter_1 exited with code 1
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.