-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cisco ISE Function Not Working #11363
Comments
Hi @macna, Did you follow this step as well? - #10070 (comment) |
Hi @v-sudkharat - we've checked the configuration in ISE and those options are enabled, as are several others. Are only certain categories supported by this parser? |
@macna, can you send the logs in below mail ID to check the format: v-sudkharat@microsoft.com |
@macna, Waiting for logs to check on this issue. Thanks! |
Hi @macna, since we have not received a response in the last 5 days, we are closing your issue as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation. |
Hi, apologies @v-sudkharat , I've forwarded you an example of the messages. Please reopen the issue. |
@macna, No problem. |
@macna, we have checked the logs which shared via a mail, there is no could you please check with the Cisco end configurations set up correctly? and also, please check the RAW log to ensure it having in correct format. |
One of the customers was having parsing issue, so we shared the modified parser with some changes. So is below one working for you too? |
I tried this parser in the beginning but it has the same problem. The order is wrong because off the additional log field in the beginning off the log string |
Hi @v-sudkharat - the syslog column is present; otherwise, the function wouldn't parse any data. I think @krisbogaerts has the right of it - the function needs to be updated to facilitate the log format now coming out of ISE appliances. |
@macna, While checking on shared CSV file, could not fount the |
Hi @v-sudkharat, just so I'm clear, do you want the raw data from the syslog table or the parsed data after the function has run on it? |
@macna, The RAW logs for syslog to understand the new format and you can also share the SyslogMessage by using below query -
Thanks! |
Hi @v-sudkharat please see output below: I have emailed you the log export separately. |
@macna, Received the logs, we will check on it and get back to you. Many Thanks! |
Hi @macna, Can you run below Parser in workspace and let us know the result -
|
Hi @v-sudkharat - that does seem to work better. We are seeing, however, that every other line is now missing the event ID and severity: |
@macna, The data which you have shared with us, is in 2 different format which highlighted into the below screenshot and due that the parser is able to parse the supported 1st Thanks! |
@macna , Anything for us? |
Hi @macna, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 11-12-2024 date, we will be closing this issue. |
Hi @v-sudkharat. I think we understand the problem, but is the parser going to be updated to correctly parse both message types? |
@macna , it's quite difficult, as the message from source has been different. Tying to fill the blank spaces and also added new columns into the parser
Many Thanks! |
@macna, Did you get a chance to check on above comment? Could you please confirm if your issue resolve, for ticket closer. Thanks! |
Hi @v-sudkharat, thanks for this. I have colleagues testing and will let you know how they get on. |
@macna, Noted. Please let us know once done. Thanks! |
@macna, Any update on testing? waiting for the response. |
Hi @v-sudkharat - we have performed some testing of the new parser but continue to have problems unfortunately. It seems that the EventId column is not being parsed correctly, and so we find that the extended event descriptions in the EventName datatable are not showing as expected. |
Describe the bug
The "CiscoISEEvent" function included with the Cisco ISE solution parses the data incorrectly, resulting in data appearing in the incorrect columns.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Data to be returned in the correct columns.
Screenshots
Desktop (please complete the following information):
Additional context
I believe this to be the same issue as #10070
The text was updated successfully, but these errors were encountered: