Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1216613%22%20slang%3D%22en-US%22%3EIngesting%20JSON%20formatted%20data%20into%20Azure%20Data%20Explorer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1216613%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20know%20that%20you%20can%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-explorer%2Fingest-data-overview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Eingest%3C%2FA%3E%20JSON%20formatted%20data%20into%20Azure%20Data%20Explorer%3F%3C%2FP%3E%0A%3CP%3EStart%20by%20setting%20up%20a%20cluster%20and%20database%2C%20and%20then%20decide%20which%20JSON%20file%20format%20your%20source%20data%20is%20in%3A%20%3CSTRONG%3EJSON%3C%2FSTRONG%3E%2C%20or%20%3CSTRONG%3EmultiJSON%3C%2FSTRONG%3E.%20It%20makes%20a%20difference%20because%20with%20JSON%2C%20each%20line%20in%20the%20input%20data%20has%20one%20JSON%20record%2C%20but%20for%20multiJSON%2C%20the%20parser%20reads%20a%20record%20from%20the%20previous%20position%20to%20the%20end%20of%20a%20valid%20JSON.%3C%2FP%3E%0A%3CP%3EWhen%20you%20ingest%20JSON%20formatted%20data%2C%20you'll%20need%20to%20specify%20the%20format%20and%20map%20the%20JSON%20source%20entry%20to%20its%20target%20column%20using%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fkusto%2Fmanagement%2Fmappings%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Edata%20mapping%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3EYou%20can%20use%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-explorer%2Fingest-json-formats%3Ftabs%3Dkusto-query-language%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKQL%2C%20and%20other%20languages%3C%2FA%3E%20to%20ingest%20many%20types%20of%20records%20and%20arrays.%3C%2FP%3E%0A%3CP%3ERead%20more%20about%20this%20topic%20with%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-explorer%2Fingest-json-formats%3Ftabs%3Dkusto-query-language%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Eexamples%20and%20sample%20data%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3ERelated%20information%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EIngesting%20data%20using%20the%20Azure%20Data%20Explorer%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-explorer%2Fpython-ingest-data%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EPython%3C%2FA%3E%20library%3C%2FLI%3E%0A%3CLI%3EIngesting%20data%20using%20the%20Azure%20Data%20Explorer%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-explorer%2Fnet-standard-ingest-data%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E.NET%20Standard%3C%2FA%3E%20SDK%3C%2FLI%3E%0A%3CLI%3EHow%20to%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-explorer%2Fcreate-cluster-database-portal%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ecreate%20a%20cluster%20and%20database%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3EUsing%20the%20%3CA%20href%3D%22%3A%2520https%3A%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fkusto%2Fmanagement%2Fdata-ingestion%2Findex%23ingestion-properties%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eingestion%20property%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1216613%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20know%20that%20you%20can%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdata-explorer%2Fingest-data-overview%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Eingest%3C%2FA%3E%20JSON%20formatted%20data%20into%20Azure%20Data%20Explorer%3F%3C%2FP%3E%0A%3CP%3EStart%20by%20setting%20up%20a%20cluster%20and%20database%2C%20and%20then%20decide%20which%20JSON%20file%20format%20your%20source%20data%20is%20in%3A%20%3CSTRONG%3EJSON%3C%2FSTRONG%3E%2C%20or%20%3CSTRONG%3EmultiJSON%3C%2FSTRONG%3E.%20It%20makes%20a%20difference%20because%20with%20JSON%2C%20each%20line%20in%20the%20input%20data%20has%20one%20JSON%20record%2C%20but%20for%20multiJSON%2C%20the%20parser%20reads%20a%20record%20from%20the%20previous%20position%20to%20the%20end%20of%20a%20valid%20JSON.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1216613%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eadx%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Data%20Explorer%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EKusto%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

Did you know that you can ingest JSON formatted data into Azure Data Explorer?

Start by setting up a cluster and database, and then decide which JSON file format your source data is in: JSON, or multiJSON. It makes a difference because with JSON, each line in the input data has one JSON record, but for multiJSON, the parser reads a record from the previous position to the end of a valid JSON.

When you ingest JSON formatted data, you'll need to specify the format and map the JSON source entry to its target column using data mapping.

You can use KQL, and other languages to ingest many types of records and arrays.

Read more about this topic with examples and sample data.

Related information:

  1. Ingesting data using the Azure Data Explorer Python library
  2. Ingesting data using the Azure Data Explorer .NET Standard SDK
  3. How to create a cluster and database
  4. Using the ingestion property