Custom fields are not created when deploying the application

[SamirFarhat]

Hello All,
It's a great solution that we are seeing here.
I'm encountering something wired.
After importing the Designer view file. An error is thrown when loading the views : Unknown type 'SQLAuditLog_CL'
I have checked the custom fields, and i did not find any CF with this name.
Looks like the deployment operation is not creating the CFs.

[TomerWeisberg]

Hi Samir,

did you allow the code to run and import audit data into your OMS workspace? I think the type will be defined after OMS will ingest the data. Let us know if this is not the case.

Thanks, Tomer (MSFT)

[SamirFarhat]

Hi,
I followed the 'readme' file. The steps are very simple. The Web App was deployed successfully. I noticed that the App Service Plan tier is 'free', not a basic plan as the 'readme' file shows.
The job run several times, no data has been imported to OMS
Thanks for your help

[TomerWeisberg]

I will probably need to see you traces from the webapp to understand why no event was imported to OMS. You can send me the details to tomerw at Microsoft.

Thanks, Tomer (MSFT).

[MattAllison]

I had similar results and also received errors that other types were not known. I didn't recall all of them but I know that IP address was among them.

I realized that I probably didn't have much or any data in the logs at the time I did the setup - I had only created the server, not a database. I created a database and generated some audit data and could then create the dashboard but I'm not sure if everything is functioning as intended.

For example, the detail information on Database Authentication Failed doesn't show any data like I would expect (see graphic).

[ghost]

Nice solution, but ran into similar issues. Nothing is getting imported, below is what I see in the logs. The logs seem to be OK as I can open them in SSMS:
[04/19/2017 10:22:08 > 23bdfb: INFO] OMS Error: 0 : Failed processing: https://accountname.blob.core.windows.net/sqldbauditlogs/wus-te-sdb-pulse-01/wus-te-sdb-pulse01-db1/SqlDbAuditing_ServerAudit_NoRetention/2017-04-19/08_06_54_168_0.xel. Reason: System.FormatException: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters

[TomerWeisberg]

Adding few more people as I’m OOF next week. Please take a look. Thanks, Tomer. From: Felix Bodmer [mailto:notifications@github.com] Sent: Wednesday, April 19, 2017 1:25 PM To: Microsoft/Azure-SQL-DB-auditing-OMS-integration <Azure-SQL-DB-auditing-OMS-integration@noreply.github.com> Cc: Tomer Weisberg <tomerw@microsoft.com>; Comment <comment@noreply.github.com> Subject: Re: [Microsoft/Azure-SQL-DB-auditing-OMS-integration] Custom fields are not created when deploying the application (#6) Nice solution, but ran into similar issues. Nothing is getting imported, below is what I see in the logs. The logs seem to be OK as I can open them in SSMS: [04/19/2017 10:22:08 > 23bdfb: INFO] OMS Error: 0 : Failed processing: https://accountname.blob.core.windows.net/sqldbauditlogs/wus-te-sdb-pulse-01/wus-te-sdb-pulse01-db1/SqlDbAuditing_ServerAudit_NoRetention/2017-04-19/08_06_54_168_0.xel<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccountname.blob.core.windows.net%2Fsqldbauditlogs%2Fwus-te-sdb-pulse-01%2Fwus-te-sdb-pulse01-db1%2FSqlDbAuditing_ServerAudit_NoRetention%2F2017-04-19%2F08_06_54_168_0.xel&data=02%7C01%7Ctomerw%40microsoft.com%7Cc02e24abf2794964a7e408d4870e53ea%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636281942988477581&sdata=5yvqGGQCJoWtG%2FUGicpK9RnpdYLWGr1vX5Pvnwtvyv8%3D&reserved=0>. Reason: System.FormatException: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FAzure-SQL-DB-auditing-OMS-integration%2Fissues%2F6%23issuecomment-295205922&data=02%7C01%7Ctomerw%40microsoft.com%7Cc02e24abf2794964a7e408d4870e53ea%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636281942988477581&sdata=RMpPhgISWh9YPb%2FObxWgLmrxipVvPsZPRV%2BjGaJOaqE%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARJ2758ZEiVlrzlDcpjIRQExIUSRuLYMks5rxeD4gaJpZM4L8VOK&data=02%7C01%7Ctomerw%40microsoft.com%7Cc02e24abf2794964a7e408d4870e53ea%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636281942988487589&sdata=sxChdKtFQsaScfl%2FNWjYnBtsr6Hx8OLZ8MnJDxRfvkE%3D&reserved=0>.

[GalGrinblat]

Hi,

It looks like the OMS workspace key is incorrect or bad formatted which cause the operation to fail.
Please Retrieve the OMS workspace key (see: prerequisites under "Retrieve OMS Workspace ID and Access key") and update the app service application settings as shown in the folowing screen shot:

Thanks,
Gal

[ghost]

Gal,

Thanks for the feedback I re-installed and it worked.

Thanks.
Felix