Abstract: Some embodiments support embedding of a notebooks software component in a surrounding host application, thereby promoting consistency of notebook user interfaces and user experiences between different kinds of applications. For instance, the notebook access added to an integrated development environment (IDE) may be aesthetically consistent with the notebook access added to a business analytics tool from the same vendor as the IDE. Departures from the aesthetic are still supported, e.g., a notebook access provided in a video gaming environment to teach gamers programming skills may have the same aesthetic as the simulated world of the video game, rather than an IDE aesthetic or an enterprise software aesthetic. Direct integration or proxied integration architectures may be used. Efficiencies may be gained by distinguishing between notebook viewing, editing, and executing operations, and providing more computationally expensive resources only as needed for the notebook access being performed.

Abstract: A rule-based attribution mechanism analyzes documents having different types of data in different formats through the application of script-based rules that apply a tag to the document identifying the type of sensitive data that is contained in the document. Documents having similar tags are aggregated so that the sensitive data is scrubbed from the document leaving the telemetric data available for downstream processing. The scrubbing entails different actions, such as, eliminating the sensitive data, obfuscating the sensitive data, and converting the sensitive data into a non-sensitive value.

Abstract: A rule-based attribution mechanism analyzes documents having different types of data in different formats through the application of script-based rules that apply a tag to the document identifying the type of sensitive data that is contained in the document. Documents having similar tags are aggregated so that the sensitive data is scrubbed from the document leaving the telemetric data available for downstream processing. The scrubbing entails different actions, such as, eliminating the sensitive data, obfuscating the sensitive data, and converting the sensitive data into a non-sensitive value.

Abstract: Some embodiments support embedding of a notebooks software component in a surrounding host application, thereby promoting consistency of notebook user interfaces and user experiences between different kinds of applications. For instance, the notebook access added to an integrated development environment (IDE) may be aesthetically consistent with the notebook access added to a business analytics tool from the same vendor as the IDE. Departures from the aesthetic are still supported, e.g., a notebook access provided in a video gaming environment to teach gamers programming skills may have the same aesthetic as the simulated world of the video game, rather than an IDE aesthetic or an enterprise software aesthetic. Direct integration or proxied integration architectures may be used. Efficiencies may be gained by distinguishing between notebook viewing, editing, and executing operations, and providing more computationally expensive resources only as needed for the notebook access being performed.

Abstract: A rule-based attribution mechanism analyzes documents having different types of data in different formats through the application of script-based rules that apply a tag to the document identifying the type of sensitive data that is contained in the document. Documents having similar tags are aggregated so that the sensitive data is scrubbed from the document leaving the telemetric data available for downstream processing. The scrubbing entails different actions, such as, eliminating the sensitive data, obfuscating the sensitive data, and converting the sensitive data into a non-sensitive value.

Abstract: A real-time event processing system receives event data containing telemetric data and one or more personal identifiers. The personal identifier in the event data is replaced with an obfuscated value so that the telemetric data may be used without reference to the personal identifier. A reversible map is used to reverse the obfuscated personal identifier to its original value. In the case when a request is received to delete the mapped personal identifier, the link to the entry in the reversible map is broken by associating the personal identifier with a different obfuscated value.

Abstract: A rule-based attribution mechanism analyzes documents having different types of data in different formats through the application of script-based rules that apply a tag to the document identifying the type of sensitive data that is contained in the document. Documents having similar tags are aggregated so that the sensitive data is scrubbed from the document leaving the telemetric data available for downstream processing. The scrubbing entails different actions, such as, eliminating the sensitive data, obfuscating the sensitive data, and converting the sensitive data into a non-sensitive value.

Abstract: An offline batch processing system classifies sensitive data contained in consumer data, such as telemetric data, using a manual classification process and a machine learning model. The machine learning model is used to recheck the policy settings used in the manual classification process and to learn relationships between the features in the consumer data in order to identify sensitive data. The identified sensitive data is then scrubbed so that the remaining data may be used.

Abstract: A real-time event processing system receives event data containing telemetric data and one or more personal identifiers. The personal identifier in the event data is replaced with an obfuscated value so that the telemetric data may be used without reference to the personal identifier. A reversible map is used to reverse the obfuscated personal identifier to its original value. In the case when a request is received to delete the mapped personal identifier, the link to the entry in the reversible map is broken by associating the personal identifier with a different obfuscated value.

Abstract: Debugging and testing are aided by removing portions of software which are not relevant to a particular scenario. Upon replay, scenario behavior occurs. A reduction tool selects a function exercised during the replay, disables it to provide a test version of the software, replays the scenario to the test version to produce a candidate behavior, and compares the candidate behavior to the scenario behavior. When the candidate behavior matches the scenario behavior the tool removes the disabled function, thereby providing a reduced version of the software which is functionally equivalent to the full version but has fewer functions to manage. The tool may also remove unexercised code. Trimming unexercised code and reducing exercised but irrelevant code may be interleaved. Caching, dynamic uniform resource locator mapping, hypertext markup language code refactoring, and/or avoidance of certain random elements may also facilitate exhibiting, testing, or debugging web applications.

Abstract: A test result analyzer for processing results of testing software. The analyzer has an interface emulating the interface of a traditional data logger. After analyzing the test results, selected results may be output to a log file or otherwise reported for subsequent use. The test result analyzer compares test results to results in a database of historical data from running test cases. The analyzer filters out results representative of fault conditions already reflected in the historical data, thereby reducing the amount of data that must be processed to identify fault conditions.