I installed ELK on Ubuntu, all is working fine. (being able to browse to Kibana from http://sample:5601/app/kibana)
I installed Kibana time-lion plugin following these guidelines:
https://www.elastic.co/blog/timelion-timeline
mlast#elk:/$ sudo docker run -i -t kibana /bin/bash
root#2816533dd8a5:/# cd bin
root#2816533dd8a5:/bin# kibana plugin -i kibana/timelion
Installing timelion
Attempting to extract from https://download.elastic.co/kibana/timelion/timelion-latest.tar.gz
Downloading 3381940 bytes....................
Extraction complete
Optimizing and caching browser bundles...
Plugin installation complete
After installation I was expecting to see the Kibana app chooser icon but it does not exist. moreover when trying to browse to this url http://sample:5601/app/timelion I am getting
{"statusCode":404,"error":"Not Found","message":"Unknown app timelion"}
What seems to be the issue? I also trying to install other Kibana plugin such as Marvel but still, I am not being able to see the icon
You need restart kibana for load the new plugins.
Additional you are using docker, add persistence in plugins
sudo docker run -i -t -v /to/path/host/plugins:/opt/kibana/installedPlugins kibana
Related
I am trying to debug an application I have deployed to google cloud app engine. Reading the docs, I figured out that in order to do so I have to enter the debug mode using
gcloud app --project [Project ID] instances enable-debug
afterwards I am able to SSH into my instance and access root. Now I would like to edit some of the files. However, trying to use vim or nano does not seem to work.
Is there a way to edit those files without re-deploying the entire app?
Once you SSH into the App Engine instance and open a shell into the Docker container, you'll need to download the package list before installing nano or vim:
apt-get update && apt-get install nano
Then you can edit your app's files (which are in /app):
nano composer.json
The deployed app runs live code. It is not generally feasible to edit it. Moreover, changes made to the running container are not permanent; in fact they and are lost at the first re-start.
You may find some information on the Debugging an Instance page.
Unrelated to the above, an actual command-line editor is offered in the cloud shell.
I tried to run the plugin generator included in Kibana 7.0.0-alpha, but generate_plugin.js script doesn't exist after upgrading Kibana by running the .deb installation file for Kibana 7.0.0-alpha. I know I successfully installed Kibana 7.0.0-alpha because it runs properly through the browser. In addition, I attempted to run the script directly from clone of the git repo but I got a "Error: Cannot find module '#kbn/plugin-generator'" error. Do I have to manually define the generate_plugin script? I wasn't even able to find a scripts folder within my Kibana installation directory.
I am trying to write my first application with hyperledger.
I am running on Windows 10 pro 64-bit (10.0, Build 15063).
I have followed the prerequisites below and have installed all the appropriate dependencies from the guide: http://hyperledger-fabric.readthedocs.io/en/latest/prereqs.html.
I am able to use the out of the box scripts ./byfn.sh -m generate to set up my first network.
While trying to execute the script (./startFabric.sh), I get the error
# don't rewrite paths for Windows Git Bash users export MSYS_NO_PATHCONV=1
docker-compose -f docker-compose.yml down
Removing network net_basic
docker-compose -f docker-compose.yml up -d ca.example.com
orderer.example.com peer0.org1.example.com couchdb
Creating network "net_basic" with the default driver
Pulling couchdb (hyperledger/fabric-couchdb:latest)...
ERROR: manifest for hyperledger/fabric-couchdb:latest not found
So I got to https://hub.docker.com/r/hyperledger/fabric-couchdb/
and see that there is no latest tag for fabric-couchdb image
and I download successfully:
docker pull hyperledger/fabric-couchdb:ppc64le-1.0.2
Status: Downloaded
newer image for hyperledger/fabric-couchdb:ppc64le-1.0.2
but I am still receiving the same error
ERROR: manifest for hyperledger/fabric-couchdb:latest not found
even though I can see with docker images that I do have the fabric-couchdb image
REPOSITORY TAG IMAGE ID
CREATED SIZE
hyperledger/fabric-ca latest 7e53be14f804 3
weeks ago 238MB
hyperledger/fabric-ca x86_64-1.0.2 7e53be14f804 3
weeks ago 238MB
hyperledger/fabric-couchdb ppc64le-1.0.2 3a7f22fa9375 3
weeks ago 1.61GB
Is there a way I can get the startFabric.sh to execute properly without the latest couchdb tag?
I fixed the problem.
In "~/abric/fabric-samples/basic-network/docker-compose.yml", in the couchdb section, change the line:
image: hyperledger/fabric-couchdb
to
image: hyperledger/fabric-couchdb:x86_64-0.4.6
This is because Docker automatically pulls the latest image if no specific tag is provided.
I had the same issue a couple of days back on Ubuntu 16! Unfortunately, I missed a step "Download Platform-specific Binaries" in the setup process which didn't installed few required tools like Cryptogen.
Install the tools using the command curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/v1.0.6/scripts/bootstrap.sh | bash -s 1.0.6
Set the path to the bin directory of the installation folder export PATH=<path to download location>/bin:$PATH
Hope it works for you
It seems that you've got a wong edition of hyperleddger/fabric-couchdb, the ppc641e-1.0.2 should go to x86_64-1.0.2. Once right, you can call docker tag to tag it be latest.
I am trying to install sense plugin for elasticsearch/kibana.
I have successfully installed Kibana but when following the instruction on https://www.elastic.co/guide/en/sense/current/installing.html
I type :
./kibana plugin --install elastic/sense, on the bin directory inside kibana folder, and I get :
ERROR unknown command plugin
Usage: bin/kibana [command=serve] [options]
Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch.
Commands:
serve [options] Run the kibana server
help <command> Get the help for a specific command
"serve" Options:
-h, --help output usage information
-e, --elasticsearch <uri> Elasticsearch instance
-c, --config <path> Path to the config file, can be changed with the CONFIG_PATH environment variable as well. Use mulitple --config args to include multiple config files.
-p, --port <port> The port to bind to
-q, --quiet Prevent all logging except errors
-Q, --silent Prevent all logging
--verbose Turns on verbose logging
-H, --host <host> The host to bind to
-l, --log-file <path> The file to log to
--plugin-dir <path> A path to scan for plugins, this can be specified multiple times to specify multiple directories
--plugin-path <path> A path to a plugin which should be included by the server, this can be specified multiple times to specify multiple paths
--plugins <path> an alias for --plugin-dir
I can't figure out why I get this error, how can I install sense plugin then ?
As wuxiwei said, Sense was renamed to Console and it is already available on Kibana 5.*. In Kibana, just click on Dev Tools:
Sense was renamed to Console and is built into Kibana 5. You can find it by clicking on the Dev Tools application.
Sense is now included as Console in Kibana 5.0. You can view the following link:
https://github.com/elastic/sense/blob/master/README.md
There is no need of installing sense seprately, as it is now included as Console. elasticsearch and kibana should be running then Console can be found on :
http://localhost:5601/app/kibana#/dev_tools/console
Manual Downloaded it
Kibana’s bin/plugin script requires direct internet access for downloading and installing Sense. If your server doesn’t have internet access, you can download the Sense tar file from the following link: https://download.elasticsearch.org/elastic/sense/sense-latest.tar.gz
Once downloaded you can install Sense using the following command:
$ bin/kibana plugin -i sense -u file:///PATH_TO_SENSE_TAR_FILE
I am using kibana 6.5.4 and now we use Dev Tools instead of using sense plugin. you can input: http://127.0.0.1:5601/app/kibana after starting your new version of kibana services and you will find Dev Tools on the left side.
It was renamed to Console. After you start Kibana, you can easily browse Console directly from http://localhost:5601/app/kibana#/dev_tools/console
I'd like to view my machine's syslogs more beautifully on an ubuntu desktop. I notice that all the kibana documentation is oriented towards remote servers (which makes sense). However, how would I securely view the same information about my local machine?
Here are some things I've read that were not helpful because they were designed for remote access:
https://www.digitalocean.com/community/tutorials/how-to-use-logstash-and-kibana-to-centralize-logs-on-centos-7
Kibana deployment issue on server . . . client not able to access GUI
http://www.elasticsearch.org/overview/kibana/installation/ which has the following problems:
there is no config.js to open in an editor per step 2, you can see this very plainly on their github page: https://github.com/elasticsearch/kibana
running
~/kibana/src/server/bin$ bash kibana.sh
The Kibana Backend is starting up... be patient
Error: Unable to access jarfile ./../lib/kibana.jar
How do I install kibana locally?
Not sure if you're still looking for an answer, but for future searchers:
What you can do is download elasticsearch - http://www.elasticsearch.org/overview/elkdownloads/
Extract it, and create a plugins subdirectory. Then, within the /plugins directory create a /kibana/_site subdirectory.
Then, download kibana using the above mentioned link. Extract the archive, then edit config.js to point to the localhost as the elasticsearch host:
elasticsearch: "http://localhost:9200",
Copy all of the contents of the folder you extracted kibana into to the /kibana/_site directory you created inside the elasticsearch folder.
Then start elasticsearch:
within the elasticsearch directory -
bin/elasticsearch
Kibana will now run off of the same 'server' as elasticsearch, on your local host.
UPDATE: Kibana 4 comes bundled with a web server now: see the docs