I am working on postgres monitoring by referring to page, and my postgres_exporter version is v0.8.0, and found some metrics missing, for example:
pg_stat_user_tables_n_tup_hot_upd
pg_stat_user_tables_idx_scan
pg_stat_user_tables_seq_scan
Is there anyone who uses these metrics? and what is the postgres_exporter version?
Thank you.
Related
Stuck with the below error while configuring dse address.yaml.
INFO [async-dispatch-1] 2021-04-17 07:50:06,487 Starting DynamicEnvironmentComponent
;;;;;
;;;;;
INFO [async-dispatch-1] 2021-04-17 07:50:06,503 Starting monitored database connection.
ERROR [async-dispatch-1] 2021-04-17 07:50:08,717 Can't connect to Cassandra, authentication error, please carefully check your Auth settings, retrying soon.
INFO [async-dispatch-1] 2021-04-17 07:50:08,720 Finished starting system.
Configured cassandra user and password in cluster-name.conf & address.yaml as well.
Any advice would be appreciated.
You've provided very little information about the issue you're running into so our ability to assist you is very limited.
In any case, my suspicion is that (a) you haven't configured the correct seed_hosts in cluster_name.conf, or (b) the seeds are unreachable from the agents.
If this is your first time installing OpsCenter, I highly recommend that you let OpsCenter install and configure the agents automatically. When you add the cluster to OpsCenter, you will get prompted with a choice on whether to do this automatically:
For details, see Installing DataStax Agents automatically.
As a side note, we don't recommend you set any properties in address.yaml unless it's a last resort. Wherever possible and in almost all cases, configure the agent properties in cluster_name.conf so it's managed centrally instead of individual nodes.
It's difficult to help you troubleshoot your problem in a Q&A forum. If you're still experiencing issues, my suggestion is to log a DataStax Support ticket so one of our engineers can assist you directly. Cheers!
I am looking at upgrading from older generation ec2 to the latest generation for example m3.medium to m5.large. Are there any steps or considerations that need to be made when making this change? I couldn't find any documentation that is linux specific, only windows specific: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/migrating-latest-types.html.
If anybody could help me I would really appreciate it.
To upgrade the instance type on AWS I usually follow this official doc
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html
However it also depends on the complexity of application running on your instance viz. just an apache server or a database? To handle that situation as #Marcin mentioned, always start with AMI of your instance and try doing any change before applying directly on production instances.
screenshot from the official doc
I am trying to connect to one of my Redshift clusters so that I can fetch data from one of the tables there. I am using Node.js for it.
I used the createCluster() method and created a cluster, but I cannot seem to find a method to read from/connect to it. The aws docs are rather confusing for me as I am new to the aws environment.
How can I connect to an existing cluster and get some data out of a table in it?
Thanks :)
npm i node-redshift
you can connect using this npm name node-redshift
https://www.npmjs.com/package/node-redshift
OR
regarding the AWS, i think this will help you
Trying to Connect to Redshift Over AWS Lambda
I was trying to make the 'node-redshift' module work before I asked this question here. I found out what I was missing out on. I had to have a security group associated with my cluster. There was no option to create a security group in my region (Asia Pacific - Mumbai). I changed the region and was able to create the group, set the appropriate port and IP and it worked.
To those who are using node-redshift, it was working fine with 12.13.1 but was not responding for 14.15.0 LTS.
Maybe you may want to check your Node version once.
I was able to connect AWS-Lambda to Redshift importing 'node-redshift' module into the Lambda Function. The most important thing while creating lambda layer try to make the layer for 'node-redshift' package for version nodejs10.x. I tried adding the layer for nodejs14.x and was struggling to make a connection to Redshift which was not happening. So after changing the version from nodejs14.x to nodejs10.x it worked. Moreover thanks to Vijender R, his answer also gave me the direction to change the versioning for working with the 'node-redshift' package.
Had the same issue, the reason - I've updated node.js. After returned it to version 11.1.0, everything works ok.
The solution is to find something instead node-redshift (since it was updated 4 years ago)
It may be worth trying to use https://www.npmjs.com/package/#aws-sdk/client-redshift-data, which seems to be maintained by AWS itself.
I'm learning containers and how they work and started learning Kubernetes. I was wondering if there is a way I can pull or extract data from a Kubernetes cluster? What I want to do is to pull data from a cluster and monitor the information that is coming from it. I googled some and came up with some clients that work on nodejs and just wanted to know if I'm heading in the right direction.
what I'm trying to do is pull data from a cluster and put it on a front end website for me to see. (Thinking of making a compare CPU usage of different clusters site)
the link in question: https://github.com/tenxcloud/node-kubernetes-client
Look into heapster (https://github.com/kubernetes/heapster) with InfluxDB and Grafana as backends. Grafana is great for the type of monitoring and comparison that you seem to be looking for. This is sometimes included. With AKS in Azure heapster is there out of the box, but InfluxDB and Grafana must be added. I think that the entire stack is present in Google's offering.
I have Container Linux by CoreOS 1353.1.0 installed and it uses etcd2 by default. I can't even find an etcd3 service file (systemctl | grep etcd only shows etcd2.service).
I wanna play with etcd3. especially because it's the default storage backend for kubernetes 1.6.
is there any way (easy or hard) to migrate from etcd2 to etcd3? when I say migrate.. I don't mind recofiguring my ignition file and reinstalling the all OS.
any information regarding the issue would be greatly appreciated.
how come ContainerOS Alpha doesn't come with etcd3?!?!
thanks!
I can use etcd-member.service to start a container image with any version that I want. it's cool !:)
more info at https://coreos.com/etcd/docs/latest/getting-started-with-etcd.html#setting-up-etcd