# US 2024/0202059 A1 · Visual alert generation in a data pipeline environment > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2024/0202059 A1 - Document ID: US20240202059A1 - Status: Published application - Kind: A1 - Application number: 18/390,035 - Filed: 2023-12-20 - Published: 2024-06-20 - Earliest claimed: 2021-08-17 - Assignees: Data Culpa, Inc. - Applicants: Data Culpa, Inc. - Inventors: J. Mitchell Haile - Web page: https://patentgrep.com/patent/US20240202059A1 ## CPC - G06F 11/0769: {Readable error formats, e.g. cross-platform generic formats, human understandable formats} - G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems} - G06F 11/076: {by exceeding a count or rate limit, e.g. word- or bit count limit} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Various embodiments comprise systems and methods to indicate when errors occur in a data pipeline. In some examples, data monitoring circuitry monitors the operations of a data pipeline. The data monitoring circuitry ingests an output data set generated by the pipeline, compares the output data set to an expected output, identifies differences between the output data set and the expected output, and determines when the magnitude of the difference exceeds an error threshold. When the error threshold is exceeded, the data monitoring circuitry generates a graphical representation of the output data set, a graphical representation of the expected pipeline output, and an animated transition from the graphical representation of the expected pipeline output to the graphical representation of the output data. The data pipeline monitoring circuitry transfers an alert that comprises the graphical representation of the expected pipeline output, the graphical representation of the output data, and the animated transition. ## Claims ### Claim 1 A data pipeline monitoring system configured to detect errors in a data pipeline, the data pipeline monitoring system comprising: processing circuitry configured to: monitor operations of the data pipeline; difference between a pipeline output and an expected pipeline output triggers an error threshold; and when the error threshold is triggered, generate graphical representations of the pipeline output and the expected pipeline output and an animated transition between the graphical representations of. ### Claim 2 (depends on 1) The system of claim 1 wherein the processing circuitry is configured to transfer an alert that comprises the graphical representations and the animated transition. ### Claim 3 (depends on 2) The system of claim 2 wherein the comprises at least one of an email or a text message. ### Claim 4 (depends on 2) The system of claim 2 wherein: the processing circuitry is configured to determine a cause for the difference between the pipeline output and the expected pipeline output; and the alert comprises contextual information that indicates the cause of the difference. ### Claim 5 (depends on 2) The system of claim 2 wherein the alert comprises a Graphics Interchange Format (GIF) file. ### Claim 6 (depends on 1) The system of claim 1 wherein: the processing circuitry is configured to determine when a difference between at least one of data values, data types, or data schema of the pipeline output and expected data values, expected data types, or expected data schema of the expected pipeline output triggers the error threshold. ### Claim 7 (depends on 1) The system of claim 1 wherein the expected pipeline output comprises a historical pipeline output. ### Claim 8 (depends on 1) The system of claim 1 wherein: the expected pipeline output corresponds to a first period of time; the pipeline output corresponds to a second period of time; and the processing circuitry is configured to select the expected pipeline based on a chronological proximity between the first period of time and the second period of time. ### Claim 9 A method of operating a data pipeline monitoring system to detect errors in a data pipeline, the method comprising: monitoring operations of the data pipeline; determining when a difference between a pipeline output and an expected pipeline output triggers an error threshold; and when the error threshold is triggered, generating graphical representations of the pipeline output and the expected pipeline output and an animated transition between the graphical representations. ### Claim 10 (depends on 9) The method of claim 9 further comprising transferring an alert that comprises the graphical representations and the animated transition. ### Claim 11 (depends on 10) The method of claim 10 alert comprises at least one of an email or a text message. ### Claim 12 (depends on 10) The method of claim 10 further comprising: determining a cause for the difference between the pipeline output and the expected pipeline output; and wherein: the alert comprises contextual information that indicates the cause of the difference. ### Claim 13 (depends on 10) The method of claim 10 wherein the alert comprises a Graphics Interchange Format (GIF) file. ### Claim 14 (depends on 9) The method of claim 9 wherein: determining when the difference between the pipeline output and the expected pipeline output triggers the error threshold comprises determining when a difference between at least one of data values, data types, or data schema of the pipeline output and expected data values, expected data types, or expected data schema of the expected pipeline output triggers the error threshold. ### Claim 15 (depends on 9) The method of claim 9 wherein the expected pipeline output comprises a historical pipeline output. ### Claim 16 A non-transitory computer-readable medium storing instructions to detect errors in a data pipeline, wherein the instructions, in response to execution by one or more processors, cause the one or more processors to drive a system to perform operations comprising: monitoring operations of the data pipeline determining when a difference between a pipeline output and an expected pipeline output triggers an error threshold; when the error threshold is triggered, generating graphical representations of the pipeline output and the expected pipeline output and an animated transition between the graphical representations. ### Claim 17 (depends on 16) The non-transitory computer-readable medium of claim 16, wherein the operations further comprise transferring at least one of an email or a text message that comprises the graphical representations and the animated transition. ### Claim 18 (depends on 17) The non-transitory computer-readable medium of claim 17, the operations further comprising: determining a cause for the difference between the pipeline output and the expected pipeline output; and wherein: the at least one of the text message or email comprises contextual information that indicates the cause of the difference. ### Claim 19 (depends on 16) The non-transitory computer-readable medium of claim 16 wherein: determining when the difference between the pipeline output and the expected pipeline output triggers the error threshold comprises determining when a difference between at least one of data values, data types, or data schema of the pipeline output and expected data values, expected data types, [[and]] or expected data schema of the expected pipeline output triggers the error threshold. ### Claim 20 (depends on 16) The non-transitory computer-readable medium of claim 16 wherein the expected pipeline output comprises a historical pipeline output.