This portal is to open public enhancement requests against IBM Cloud and its products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
IBM Cloud Support Center (https://cloud.ibm.com/unifiedsupport/cases/form) – Use this site for any IBM Cloud defect or support need.
Stack Overflow (https://stackoverflow.com/questions/tagged/ibm-cloud) – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud".
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thanks. This falls into the support/engineering engagement that Denis mentioned above.
I'll leave this specific request (to use your NTP) in the "Will not implement" status until there's compelling reason to revisit it.
Thank you both for your feedback, however:
We are trying to track the transaction from an on-prem API Connect DataPower into Bluemix Dedicated and the time stamps from APIC analytics are earlier than time stamps in the goRouter logs in the platform. We can discuss more details in a private forum if needed, but without this capability we can't effectively track latency between different hops in the request chain.
Atomic clocks are the reference for all systems relying on NTP. All our data centers use antennas or stratum zero sync sources. The local servers then become sync'ed with a highly available local stratum 1 reference, ensuring minimal drift from the atomic clock reference. When using NTP to synchronize machines, the best practice is to be as near as possible to the reference source to minimize the drift induced by network latency. This is best achieved by configuring the NTP settings to use local stratum 1 servers. Due to the very nature of NTP, synchronizing over WANs will invariably lead to greater time drift on systems between your premise machines and the ones running in the Cloud.
In order to keep all the systems you use at the same time, IBM recommends ensuring the local on-prem source be as close as possible to stratum zero, and keep the ones in the cloud sync'ed to the local reference. That will guarantee you constantly remain with a minimum drift between on-prem systems and the IBM ones.
If we have a specific incident to investigate, my team can definitely be engaged through the regular channels.
See https://en.wikipedia.org/wiki/Network_Time_Protocol for background.
From past discussions on this topic, I believe pointing a dedicated environment back to KP's ntp server going over VPN/Direct Link tunnels makes the situation worse and not better.
Can you please share some data that can help us understand where in your current logs (or other artifacts) you're seeing a difference in timestamps and what problem this is causing to you?