The levels can be toggled individually basically the same as always with the exception of console.info now having the same level as console.log.

That is the point.  Grouping the filters together is never a good idea.  Console.log, console.info, and console.error are use a lot more than it seems you think.  Go ahead and read the replies in the forum to understand better.

That's an old thread and Chrome has already restored the ability to toggle the levels individually which was broken in recent versions. There are check marks to the left of each level so you can display only errors or only warning or errors+warnings or any other combination you might need. As for console.info, it's not grouped, it was effectively replaced by console.log, which I agree is a bad decision that doesn't make much sense.

It's an old thread that is still going.  You obviously didn't read the whole thing.  What started out as a discussion about being unable to toggle the levels individually, has evolved into a discussion asking for the return of those different filters.  Yes we can now individually toggle the levels.  But they're still hard to use because some of the original filters are still grouped together making the filter useless.  What good is a filter if it doesn't filter enough?  Read the last couple pages to get a better understanding of what I'm talking about.

>some of the original filters are still grouped together

Which original levels exactly? All levels except info (which was effectively removed) are mapped directly as verbose = debug, default = log/info, warning = warning, error = error

>Read the last couple pages to get a better understanding of what I'm talking about.

I've written about the problem myself on this bugtracker before it was even discussed publicly. And I agree that the old level selector was better and far more intuitive than the new one.

I'm referring to info.  Console.log, console.info, and console.error are still used often.  Removing info was a mistake.  If anything, adding filters makes more sense than removing filters.  This is the reason many developers have switched to Firefox Developer Edition.
Chrome: Verbose, Info, Warnings, Errors
FFDE: Errors, Warnings, Logs, Info, Debug, CSS, XHR, Requests

One of the concerns in that thread is that the network tab will equally simplified.
Ultimately when it comes to developers, I believe functionality is always valued more than usability.

@Reporter: As we are seeing the behavior is same in the reported chrome version 61.0.3163.100 and an older chrome version 60.0.3072.0. Could you please mention in which version it used to work fine before. 

Thanks! 

The issue first appeared in March with the "New Console UI Changes" in Google Chrome 58.  As you can see in the thread, this has been an issue for quite a while, and support to bring back the old console continues to grow.

https://developers.google.com/web/updates/2017/03/devtools-release-notes#console

Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is by design, debug is now the same level as verbose and info is the same as log -- this was done for consistency with other common log frameworks. There's more discussion here: https://bugs.chromium.org/p/chromium/issues/detail?id=717776

I am aware of that issue.
You are obviously completely disconnected from your users.  Because that decision makes absolutely no sense.  The Dev Tools are for developers.  If you actually took time to know and understand the Dev Tools users, you would never of made the Dev Tools harder to use.  If you knew the Dev Tools users, you would of added functionality that made it easier to use.  Since your so out of touch, let me give you hint.  Developers will never support usability at the cost functionality.
Consistency with other log frameworks?  What frameworks?  Obviously not browsers.  Let's be honest here.  What do we even care about consistency with other common log frameworks that are not browser related?  It's obvious that the only reason this change was made was because someone was too lazy to switch mental modes between chrome and whatever else they were using.

I am completely aware of the discussion above.  After all I filed the bug.  What doesn't make sense is why this change was even made.  What are the other common log frameworks?  Were web developers even asked if this was a desired change?  If so, is there a record of this discussion everyone can view?