Ah, I see what you mean now from your examples. In theory, there are two points where aggregation could happen: 1. collection, and 2. display. As I pointed out, we do not aggregate the error events at collection for the Error analytics page. We collect up to the cap of 100/min - at which point we don’t aggregate, we stop collecting new ones, until the next minute. They each have a timestamp so we know when they were collected, and can order them correctly.
But you are asking about the display logic. The x-axis of the graph will not display a window of time smaller than 3 minutes. This is an artifact of the UI control we use to render the visual, not of the underlying data we store. The x-axis does not show data at the microsecond level of detail. So in your example of two errors occurring at subsequent microseconds, the two errors would look like they happened at the same time on the graph, the same second (count of two). We don’t render the data at that level of microsecond precision on the graphs. In your example, the graph would show two errors happening at the same second on the graph.
If you want the exact timestamps, you have a couple ways to see that. You could click one of the corresponding error traces in the table below the chart. Or, you could click on the “View in Insights” chart seatbelt item that appears when you mouse over the chart. That will open Insights in a new window, and execute the exact query used to generate that graph you are looking at. You can use that to explore the data at the level of precision you are looking at.