- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello!
An RDS event indicates a change in the Amazon RDS environment. Note: Amazon RDS emits events on a "best effort" basis. We recommend that you avoid writing programs that depend on the order or existence of notification events because they might be out of sequence or missing. For more information, see: [+] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-cloudwatch-events.sample.html
Also, Amazon RDS doesn't guarantee the order of events sent in an event stream. The event order is subject to change. For more information, see: [+] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.overview.html
DB instance events will send an "Event ID" based on the "Event Message" as mentioned in the document: [+] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.Messages.html#USER_Events.Messages.instance
In your example, there is no "Event ID" that was associated with the "Event Message," like "Read replica has been disconnected from xxxxx. Restarting Postgres," so that is the reason you haven’t received any EventID. Sometimes, DB instance events will send "Null" as an "event ID" for some of the "Even Messages," as mentioned in the below example.
Event Source : db-instance
Identifier Link: https://console.aws.amazon.com/rds/home?region=us-east-1#dbinstance:id=db1
SourceId: db1
Notification time : 2022-11-21 13:05:37.446
Message : Slave is disconnected from the master and is attempting to reconnect.
Event ID : http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.html#null
Also, I could see in both of the examples, "Source ID" is the same as "test-instance1." If you want to capture the events of a read replica, then you should create a separate event subscription for that particular read replica. For more information, see: [+] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.Subscribing.html
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr