I am having a difficulty connecting Kibana with Amazon Redshift.
Is there a way to connect Kibana without Elasticsearch?
Is there a way to directly connect Kibana with Amazon Redshift for visualisation?
No. You have to ingest the data in elastic from beat/ logstash and then use kibana for the visualization.
No. Kibana only works with Elasticsearch.
Related
I am connecting my tableau to Splunk through the ODBC connector.
So, Splunk data are pulled into Tableau where I create the dashboard and host it in Tableau server.
But, I want to know behind the scene where does Splunk dumb data so that Tableau is able to utilize it? I heard it's in the Tableau data engine, but not sure if it's remote or local.
My company has a hard outbound network firewall rule that blocks everything except port 443. This blocks Mongo Compass from doing a direct connect to the cosmosdb via connection string. Is there any way to connect it to the Gateway API? Or are there any other desktop UI's that will work with Azure Gateway?
It's not possible to change the port for a MongoDB API account on Cosmos DB.
You can connect to the Mongo shell in the Azure Portal for your Cosmos DB account as that is over port 443, but there's no option I know of that allows you to connect to it.
I am trying to connect to a redshift cluster using aginity tool but see this below error.
Error-message
I am able to connect to other cluster within the same aws account. The cluster to which I am able to connect is in "us-east-1" region. The cluster to which I am not able to connect is in "us-west-2" region. That is the only difference. All other parameters/configurations are same.
I verified inbound rules in security group, ssl-mode in redshift cluster parameter group and if redshift role was attached to the cluster. They are fine.
I tried googling the error message but it didn't help. I am stuck with this since a day. Any help is highly appreciated. Thanks in advance.
Typically, 08S01 is a network communications error. You've confirmed that the AWS side is properly configured, but do you have an on-prem firewall that could be causing an issue? One way you can test network connectivity is telneting to the instance port to confirm that it's reachable.
Have you tried using Aginity Pro, which uses the Redshift JDBC driver. One thing that's nice is you can copy the JDBC connection screen to the cli and isolate that the issue isn't with with application.
As Kibana is the webUI for elasticsearch, it is better make it high availability. After reading the doc and make a demo, i can not find a way to set up two Kibana instances simultaneously for a single Elasticsearch cluster.
After some deep leaning about Kibana, i finally find that Kibana will store its data and configuration about dashboard and searches in the backend ES. This way Kibana is just like a proxy and ES serves as the DataBase for it.
So, the answer is yes. Kibana supports High Availability through ES.
You could simply change the server.port value to another free port (ie: something like 6602) in your kibana yml since 5601 is the default. Hence you're pointing to the same ES instance and having two (one running on the default port and the other running on port 6602) kibana instances as well.
So I've recently started working with a client that has a Wordpress site run totally off Amazon Cloud Services. As part of some new work I'm doing for them, I need to directly access the database.
I looked at the most recent bill, and the charges I see from amazon are for:
Amazon Elastic Compute Cloud
Amazon CloudFront
AWS Data Transfer
Amazon Simple Storage Service
Amazon SimpleDB (however the charge is $0.00)
I see no charges for RDS or for another database service they provide, however, the wp-config lists localhost as the connection info.
So my question is, is there a way to setup a MySQL database on one of these services? I'm thinking no, and it's possible the database is on another account?
Any help is appreciated!
Yes, Elastic Compute Cloud (ec2). AWS does over an RDS service for a managed MySQL option, but you don't have to host it that way. Currently it appears MySQL is hosted on the same instance as WordPress is installed on.