-
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
GoogleWorkspaceReports Data Connector - API start time error #9617
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 @s-khan14 , Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 19Dec2023. Thanks! |
Hi @s-khan14 ,The start time and end time both are same ,so there is an issue,please check the followiing the statemarkerfile share in azure containers and it has start time based on last run 2.Please check the delays configured in function app settings as the end time is based on that as there are no default delays configured in code Please let me know if you have any isuses,if can have a call and do further troubleshooting |
This is the content of funcstatemarkershare.
Still the function is grabbing timestamps other than this. Suggestion Why:
Note: I was able to solve the problem by doing a manual deployment via VS code - Not from ARM template |
Hi @s-khan14 , Sorry to hear this issue, got the issue, but want to have more details, so can proceed with changes, Want to have these data points based on that will do the changes,Could you please share couple of time slots and email id,so will block the calendar. |
@s-khan14 Gentle Reminder,got the issue, but want to have more details, so can proceed with changes, |
Hi @v-muuppugund, sorry for the delayed response. you can contact me at this email and then we can arrange a meeting from there. |
Hi @s-khan14, Apologies for the delayed response,Will schedule a teams meeting, please let me know if this time isn't convenient |
Hi @s-khan14 ,I waited for some time in the call today,as you are unable to join will work on changes and share package,please let me know if you have any concern |
Did you add the right email address to the invite? I never got the teams invite. Checked both spam and inbox. |
Yes @s-khan14 , I am unable to open this email and asked my collogue to open it and got the email as i.e. [maced73@yahoo.com] (mailto:maced73@yahoo.com), Could you please drop an email to (v-muuppugund@microsoft.com) . |
Hi @s-khan14 ,Gentle Reminder,, I am unable to open this email and asked my collogue to open it and got the email as i.e. [maced73@yahoo.com] (mailto:maced73@yahoo.com), Could you please drop an email to (v-muuppugund@microsoft.com) . |
Description
The recent update to GoogleWorkspaceReport Data Connector has caused function app to fail. The python script uses a start_time and end_time to fetch logs for GoogleWorkspaceAPI. Start_date is based on past_time, that depends on Function App's state. The function app state is returning unexpected date on first run.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If Function App state returns a date more that 24h in the past, use the default start_time parameter (which is 1 day as of now).
Error Message
Something wrong while getting the results. Exception error text: <HttpError 400 when requesting hxxps://admin.googleapis.com/admin/reports/v1/activity/users/all/applications/user_accounts?maxResults=1000&startTime=2022-11-21T20%3A00%3A00.000Z&endTime=2022-11-21T20%3A15%3A00.000000Z&alt=json returned "Invalid request: Start time and end time should be within last 180 days. Start time should be less than end time.". Details: "[{'message': 'Invalid request: Start time and end time should be within last 180 days. Start time should be less than end time.', 'domain': 'global', 'reason': 'invalid'}]">
Additional context
The text was updated successfully, but these errors were encountered: