-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
InAndOut Analysis using ITmfDataProviderConfigurator extension
Note: - Used through trace server - Multiple instances allowed - configuration is applied to all traces in experiment - configuration is not applied to experiment - Eclipse is using legacy InAndOut analysis config which allows one configuration per trace only and which integrated in the Eclipse UI [Added] InAndOut Analysis using ITmfDataProviderConfigurator extension Signed-off-by: Bernd Hufmann <[email protected]>
- Loading branch information
Showing
8 changed files
with
604 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
59 changes: 59 additions & 0 deletions
59
analyses/org.eclipse.tracecompass.incubator.inandout.core/schema/in-and-out-analysis.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
{ | ||
"$schema": "https://json-schema.org/draft/2020-12/schema", | ||
"$id": "https://org.eclipse.tracecompass/in-and-out-analysis.json", | ||
"title": "InAndOut Analysis", | ||
"description": "Custom Execution Analysis schema", | ||
"type": "object", | ||
"properties": { | ||
"name" : { | ||
"type": "string", | ||
"description": "The name of this InAndOut configuration" | ||
}, | ||
"description" : { | ||
"type": "string", | ||
"description": "The descrition of this InAndOut configuration" | ||
}, | ||
"specifiers": { | ||
"description": "array specifiers", | ||
"type": "array", | ||
"items": { | ||
"type": "object", | ||
"properties": { | ||
"label": { | ||
"type": "string", | ||
"descritpion": "The label of the identifier" | ||
}, | ||
"inRegex": { | ||
"type": "string", | ||
"descritpion": "The IN regular expression" | ||
}, | ||
"outRegex": { | ||
"type": "string", | ||
"descritpion": "The OUT regular expression" | ||
}, | ||
"contextInRegex": { | ||
"type": "string", | ||
"descritpion": "The context IN regular expression" | ||
}, | ||
"contextOutRegex": { | ||
"type": "string", | ||
"descritpion": "The context OUT regular expression" | ||
}, | ||
"classifier": { | ||
"type": "string", | ||
"descritpion": "The classifier" | ||
}, | ||
"required": [ | ||
"label", | ||
"inRegex", | ||
"outRegex", | ||
"contextInRegex", | ||
"contextOutRegex", | ||
"classifier" | ||
] | ||
} | ||
} | ||
} | ||
}, | ||
"required": ["name", "specifiers"] | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.