nice interface indeed, but missing the device names It only shows the device ID so it`s now more difficult to identify messages from a particular device when tracking or troubleshooting. It was very useful just to see the device name

I’m also missing the device name. While monitoring / debugging it’s easier to have displayed “Product_14” than the device ID…
Previously, at a glance I knew that “Product_35” was in good shape and “Product_49” needed something.
Now I had to look up in a table who is 420737333032000344363431…
Really it’s a pain to read.

Correct - console.particle.io/devices Once you have more than a handful of devices the event log becomes like watching a spinning wheel! All the devices I have are products so I go in through products then devices to a specific device. I see the point being made now - even the filter does not help because you cannot filter by device name only device ID. I guess it is because someone in Particle is thinking products and through that route to the individual device event logs.

I guess it is because someone in Particle is thinking products and through that route to the individual device event logs.

in the product or individual device view you can only see the events published by the devices. You cannot see the intermediate events sent by Particle or the webhook responses received from the destination server which are helpful in debugging or monitoring

I am in total agreement about device names vs. IDs, and brought this up internally today. It turns out there’s a performance impact in the device name retrieval process, which can be significant for large device deployments. That said, the ability to see device names again in Events has already been added to the to-do list; the team has a couple ideas about how to mitigate the performance hit.

But really folks, how hard is it to memorize ten or twenty 24-character Device IDs?

I pushed an update that contains the 2 items above. Device names are now displayed in the table and a new filter was added: devicename (ex. devicename:temp-sensor) (usage details are also available inside the ‘ADVANCED’ menu).

@stefanmoraru Many thanks for these changes, could I ask that the sort buttons are fixed on the device name column neither the up (z-a) or the down (a-z) sorts work properly. My device names are actually serial numbers in the format xxxx999999 and having the ability to sort these in order would save time. The work around is to search for the device name - thankfully that works.

Thanks for the feedback @armor. Currently sorting by different fields is not implemented. By default events are sorted by date.

Your suggestion with enabling sorting by other fields is amazing and was added to the backlog. Currently I have a few other things in progress and can’t tell you exactly when this will get implemented.