-
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
Tenable.io Vulnerability Management log trimming issue #9705
Comments
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal. |
Hi @Andy298, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 09-01-2024 Thanks! |
Hi @Andy298, there can be more amount of data on your selected time range. so could you please select it for 24 hr and check whether you are getting same warning message on it - Thanks! |
@v-sudkharat hi there. Nope, still the same message sorry. |
@Andy298, thanks for your response. we will check on it and get back to you by - 12-01-2024. |
Hi @Andy298, I hope you are doing well. This issue requires further investigation, so we have checked the solution and found that, this solution is supported by Tenable, which is partner-supported. As of now, we are not authorized. We kindly request that you raise a support ticket with the Tenable support team. |
We've connected the Tenable.io Vulnerability Management (using Azure Function) data connector, however we're seeing the following attached LAW operational error on a daily basis.
The following fields' values output of type Tenable_IO_Vuln_CL have been trimmed to the max allowed size, 32766 bytes. Please adjust your input accordingly. (1)
The text was updated successfully, but these errors were encountered: