We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
An analog of LOG_HADR_WAIT_TIME monitor element is needed at the agent level
Sometimes it's very useful to understand HADR influence on the transaction performance.
We do have a couple of related elements - LOG_WRITE_TIME and LOG_HADR_WAIT_TIME at the whole database level, but their values can't help us to understand, if HADR communications significantly slow down particular statements, transactions, workloads, etc.
The only more or less meaningful attempt to calculate HADR influence on user transactions is like as below for whole database:
Do not place IBM confidential, company confidential, or personal information into any field.