Downloading csv of switch logs seems to ignore filter parameters

Getting noticed

Downloading csv of switch logs seems to ignore filter parameters

Hello all,


We have a need to download switch event logs for a few specific switches.  When I put the switch name in the filter field I see only the logs for that switch, but when I download the events to CSV I get logs for a ton of unrelated switches.  I tried this several times and I get the same problem each time.  Am I missing something or is the download-to-csv feature broken?

7 Replies 7
Kind of a big deal
Kind of a big deal

Limitations of CSV/XML Reports

Downloading client information is made easy through the use of the Dashboard.

When on the client page for any Meraki product there is an option to download the current information on the right hand side of Dashboard. This information can be downloaded as either a .CSV file or .XML file. Note: Systems Manager can only be downloaded as a .CSV file.

Please refer to the list below for all the information that can be obtained through this method. Note that there is currently no way to add/remove fields from the report.

- MAC: Mac address of machine
- Description: Word/Name given to the device
- IP: IP address of machine
- Manufacturer: Person who manufactured the product, if it is a PC that was put together the Processor will be listed as the Manufacturer
- OS Fingerprint: What we can best say the OS currently is
- Notes: Notes added by the Network Administrator
- Access Status: normal/blocked/whitelisted
- Blocked Message: What the user sees if blocked
- Connection: Wired/Wireless
- First Seen At: Date first appeared on the network
- Last Seen At: Date last seen by the Dashboard
- Last Seen SSID: The SSID the device was last associated with
- XFRD: Information transferred (In bytes)
- RCVD: Information recieved (In bytes)
- SENT: Information sent (In bytes)
- Recent Authorized User: SSIDs that make use of Meraki Authentication will make use of this field.
- Last AP Mac: AP information
- Last AP Name: AP information

- Serial Number: SN of device in question, these differ based on device type and manufacturer
- System Name: Name of device as shown on the Clients page
- System Model: What type of device it is, Ex. MacBook Pro, iPad2, Virtual Machine
- Last User: Last user that logged into the device
- CPU: Current CPU of device
- RAM: Total RAM of device
- LAN IP: Self Explanatory
- Location: Where the device appears on the map (can be setup at the client edit configuration page)
- OS: Current running OS
- OS Install Date: Date when OS was installed
- SSID: Current SSID the Device is associated with
- Tags: Any tags the Network Administrator has applied to the client
- Notes: Any notes the Network Administrator has applied to the client

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

Thank you. So this means that the filter parameters are only applied to the dashboard screen display and not the downloaded .csv file?
Kind of a big deal
Kind of a big deal

Looks broken to me

Meraki Employee
Meraki Employee



Do you mind opening a case with Meraki Support? An NSE can help with scoping and identifying this known issue.

New here

i have the same issue now, it worked in May correctly as i downloaded many csv with filter options

Meraki Employee
Meraki Employee

Please open a case with Meraki Support so they can identify and attach it to the parent bug and inform you when a resolution is available.

yeah, i did it, thanks

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.