You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-manager-for-agri/how-to-set-up-audit-logs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,14 +46,14 @@ Each log follows the schema listed in the table. The table contains the field na
46
46
|**correlationId**|An optional GUID that can be used to correlate logs. |
47
47
|**identity**|Identity from the token that was presented in the REST API request. This is usually an object ID and an application ID or either of the two.|
48
48
|**location**|The region of the resource emitting the event such as "East US" |
49
-
| **properties** |For each `operationName` this contains: `requestUri` (URI of the API request), `farmerId`(farmerId associated with the request, wherever applicable),`dataPlaneResourceId` (ID that uniquely identifies the data-plane resource in the request) and `requestBody` (contains the request body for the API call associated with the `operationName` for all categories other than ApplicationAuditLogs). </br> Other than the common one's mentioned before `jobProcessesLogs` category has: </br> 1. This list fields across operationNames: </br> `jobRunType` (can be oneTime or periodic), `jobId` (ID of the job), `initiatedBy` (indicates whether a job was triggered by a user or by the service). </br> 2. This list of fields for failed farmOperation related jobs: </br> `farmOperationEntityId` (ID of the entity that failed to be created by the farmOperation job), `farmOperationEntityType`(type of the entity that failed to be created), `errorCode`(code for job failure), `errorMessage`(description of failure), `internalErrorCode`(failure code provide by the provider), `internalErrorMessage`(description of the failure provided by the provider), `providerId`(ID of the provider).
49
+
| **properties** |For each `operationName` this contains: `requestUri` (URI of the API request), `partyId`(partyId associated with the request, wherever applicable),`dataPlaneResourceId` (ID that uniquely identifies the data-plane resource in the request) and `requestBody` (contains the request body for the API call associated with the `operationName` for all categories other than ApplicationAuditLogs). </br> Other than the common one's mentioned before `jobProcessesLogs` category has: </br> 1. This list is of fields across operationNames: </br> `jobRunType` (can be oneTime or periodic), `jobId` (ID of the job), `initiatedBy` (indicates whether a job was triggered by a user or by the service). </br> 2. This list is of fields for failed farmOperation related jobs: </br> `farmOperationEntityId` (ID of the entity that failed to be created by the farmOperation job), `farmOperationEntityType`(type of the entity that failed to be created), `errorCode`(code for job failure), `errorMessage`(description of failure), `internalErrorCode`(failure code provide by the provider), `internalErrorMessage`(description of the failure provided by the provider), `providerId`(ID of the provider).
50
50
51
51
52
52
The `categories` field for Data Manager for Agriculture can have values that are listed in the following table:
53
53
### Categories table
54
54
| category| Description |
55
55
| --- | --- |
56
-
|FarmManagementLogs| Logs for CRUD operations for Farmer, Farm, Field, Boundary, Seasonal Field, Crop, CropVariety, Season, Attachment, prescription maps, prescriptions, management zones, zones, plant tissue analysis and nutrient analyses.
56
+
|FarmManagementLogs| Logs for CRUD operations for party, Farm, Field, Boundary, Seasonal Field, Crop, CropVariety, Season, Attachment, prescription maps, prescriptions, management zones, zones, plant tissue analysis and nutrient analyses.
57
57
|FarmOperationsLogs|Logs for CRUD operations for FarmOperations data ingestion job, ApplicationData, PlantingData, HarvestingData, TillageData
58
58
|SatelliteLogs| Logs for create and get operations for Satellite data ingestion job
59
59
|WeatherLogs|Logs for create, delete and get operations for weather data ingestion job
@@ -237,7 +237,7 @@ All the `categories` of resource logs are mapped as a table in log analytics. To
237
237
### List of tables in log analytics and their mapping to categories in resource logs
238
238
| Table name in log analytics| Categories in resource logs |Description
239
239
| --- | --- | --- |
240
-
|AgriFoodFarmManagementLogs|FarmManagementLogs| Logs for CRUD operations for Farmer, Farm, Field, Boundary, Seasonal Field, Crop, CropVariety, Season, Attachment, prescription maps, prescriptions, management zones, zones, plant tissue analysis and nutrient analyses.
240
+
|AgriFoodFarmManagementLogs|FarmManagementLogs| Logs for CRUD operations for party, Farm, Field, Boundary, Seasonal Field, Crop, CropVariety, Season, Attachment, prescription maps, prescriptions, management zones, zones, plant tissue analysis and nutrient analyses.
241
241
|AgriFoodFarmOperationsLogs|FarmOperationsLogs| Logs for CRUD operations for FarmOperations data ingestion job, ApplicationData, PlantingData, HarvestingData, TillageData.
242
242
|AgriFoodSatelliteLogs|SatelliteLogs| Logs for create and get operations for satellite data ingestion job.
243
243
|AgriFoodWeatherLogs|WeatherLogs|Logs for create, delete and get operations for weather data ingestion job.
@@ -271,7 +271,7 @@ All the `categories` of resource logs are mapped as a table in log analytics. To
271
271
|**JobRunType**| Available only in `AgriFoodJobProcessesLogs` table, indicates type of the job run. Value can be either of periodic or one time. |
272
272
|**JobId**| Available in`AgriFoodJobProcessesLogs`, `AgriFoodSatelliteLogs`, `AgriFoodWeatherLogs`, and `AgriFoodModelInferenceLogs`, indicates ID of the job. |
273
273
|**InitiatedBy**| Available only in `AgriFoodJobProcessesLogs` table. Indicates whether a job was initiated by a user or by the service. |
274
-
|**FarmerId**| ID of the farmer associated with the operation. |
274
+
|**partyId**| ID of the party associated with the operation. |
275
275
|**Properties**| Available only in`AgriFoodJobProcessesLogs` table, it contains: `farmOperationEntityId` (ID of the entity that failed to be created by the farmOperation job), `farmOperationEntityType`(Type of the entity that failed to be created, can be ApplicationData, PeriodicJob, etc.), `errorCode`(Code for failure of the job at Data Manager for Agriculture end),`errorMessage`(Description of failure at the Data Manager for Agriculture end),`internalErrorCode`(Code of failure of the job provide by the provider),`internalErrorMessage`(Description of the failure provided by the provider),`providerId`(ID of the provider such as JOHN-DEERE). |
276
276
277
277
Each of these tables can be queried by creating a log analytics workspace. Reference for query language is [here](https://learn.microsoft.com/azure/data-explorer/kql-quick-reference).
0 commit comments