We have set up a Postgres instance that is writing logs directly to AWS CloudWatch. We would like to be able to write our own logs for the purpose of automated processing. Unfortunately our current experiments seemed to generate logs only on the client (caller) side:

CREATE or replace FUNCTION logInfo() RETURNS void AS $$
    BEGIN
       raise notice 'Hello World!';
       raise info 'Hello World!';
    END;
$$ LANGUAGE plpgsql;

select logInfo();

Is there a way to write logs on the server side too?

We are hosting mongodb in AWS environment and planning to create incident in Servicenow using AWS Cloud watch alarm facility Has anyone integrated MongoDB Monitoring metrices with Cloud watch to create Incident ? As i am completely new to AWS, i got stuck with the integration of mongodb metrices with cloud watch Any link/lead would be highly appreciated. Thanks,

I have 1TB size mysql database for production . Now i want to migrate this database on new mysql RDS instance . Please suggest me which backup policy should i apply here like Mysqldump,XtraBackup . ?

I have a SQL Server RDS instance, running on a db.m5.xlarge (4 vCPU, 16GB RAM) with Multi AZ enabled. I am trying to determine the cause of a constant 25%-30% CPU load on the instance at a time when we know that there is very little client activity hitting the database. We've taken into account our most expensive queries and feel that they are not the cause. Regular DB maintenance such as index and statistics rebuilds has been done. The image below is a graph on a CloudWatch dashboard, monitoring database connections and CPU usage. Is there a way I can query or visualise the breakdown of CPU usage at each data point in the graph? (I'm happy to dive in and run manual queries if that is what is suggested).

We have mongo databases installed in AWS and Azure based servers. We need to monitor the Mongo databases and Cloud servers on daily basis. Is there any way to healthcheck the databases and servers ? Thanks,

https://www.postgresql.org/docs/10/logical-replication-restrictions.html States: "When the schema is changed on the publisher and replicated data starts arriving at the subscriber but does not fit into the table schema, replication will error until the schema is updated" How do we detect/query for these errors on Postgres? I tried

SELECT * FROM pg_stat_subscription;

but it shows that it received the publisher's message. It errored out when I changed publisher's schema and subcriber stopped getting updates. on AWS, the RDS cloudwatch metrics related to it is: OldestReplicationSlotLag (The lagging size of the replica lagging the most in terms of WAL data received. Applies to PostgreSQL) but I don't think this is the right metric if I want to know if my updates have corrected applied to the subscriber replica database.

I'm looking for a way to publish Aurora (pg compatible) db logs to cloudwatch. In Postgres RDS, there is an option when we "modify" the instance to enable publishing db and upgrade logs to cloudwatch, however I see no such option in Aurora. I found some documentation on how this can be achieved for Aurora MySQL but nothing for Aurora Postgres. Is this currently feasible? Appreciate any help or pointers on this. Thanks.