Absynthe: A (branching) Behavior Synthesizer
Motivation
Absynthe came about in response to the need for test data for analysizing the
performance and accuracy of log analysis algorithms. Even though plenty of real
life logs are available, e.g. /var/log/ in unix-based laptops, they do not
serve the purpose of test data. For that, we need labels, which are
difficult to obtain without an understanding the source code of the applications
that are generating these logs.
A more interesting situation arises while trying to test log analytic (and anomaly detection) solutions for distributed applications where multiple sources or modules emit their respective log messages in a single log queue or stream. This means that consecutive log lines could have originated from different, unrelated application components. Absynthe provides ground truth models to simulate such situations.
You need Absynthe if you wish to simulate the behavior of any well defined process -- whether it's a computer application or a business process flow.
Overview
Each business process or compuater application is modelled as a control flow graph (or CFG), which typically has one or more roots (i.e. entry) nodes and multiple leaf (i.e. end) nodes.
Tree-like CFG
An example of a simple, tree-like CFG generated using Absynthe is shown below.
This is like a tree since nodes are laid out in levels, and nodes at level i
have outgoing edges only to nodes at level i + 1.
Each behavior is the sequence of nodes encountered while traversing this CFG from a root to a leaf. Of course, a CFG might contain loops which could be traversed multiple times before arriving at the leaf. Moreover, if there are multiple CFGs, then Absynthe can synthesize interleaved behaviors. This means that a single sequence of nodes might contain nodes from multiple CFGs. We are ultimately interested in this interleaving behavior, which is produced by multiple CFGs.
The above screenshot shows logs generated by Absynthe. Each log line starts with a time stamp, followed by a session ID, CFG ID, and a log message. At present, the log message is simply a random concatenation of the node ID to which the log message corresponds. A single CFG might participate in multiple sessions, where each session is a different traversal of the CFG. Therefore, we maintain both session ID and CFG ID in the log line.
Directed Cyclic CFG
An example of a more complex CFG, a directed cyclic graph, is shown in the figure below. It expands the tree-like graph illustrated above by:
- attaching loops on some of the nodes,
- constructing skip-level edges, i.e. edges from a node at level
ito a node at level ≥(i + 2), and - optionally, upward edges (not shown here), i.e. edges from a node at
level
ito a node at level ≤(i - 1).
The identifiers of nodes appearing loops are helpfully prefixed with the identifiers of nodes where these loops start and finish. Moreover, loops could be traversed multiple times in a single behavior, as illustrated in the figure below.
Installation
This package requires Python >= 3.10 and depends on scipy.
The latest release is available on PyPI, simply pip install absynthe.
The main branch of this repository always contains the latest source, including any
changes merged since the last tagged release. To install from source:
# Change dir to absynthe
cd /path/to/absynthe
# Install absynthe and its dependencies
pip install .
Usage
It is possible to start using Absynthe with two classes:
- any concrete implementation of the abstract
GraphBuilderclass, which generates CFGs, and - any concrete implementation of the abstract
Behaviorclass, which traverses the CFGs generated above and emits log messages.
For instance, consider the basicLogGeneration method in
./examples/01_generateSimpleBehavior.py:
from absynthe.graph_builder import TreeBuilder
from absynthe.behavior import MonospaceInterleaving
def basicLogGeneration(numRoots: int = 2, numLeaves: int = 4,
branching: int = 2, numInnerNodes: int = 16,
loggerNodeTypes: str = "SimpleLoggerNode"):
# Capture all the arguments required by GraphBuilder class
tree_kwargs = {TreeBuilder.KW_NUM_ROOTS: str(numRoots),
TreeBuilder.KW_NUM_LEAVES: str(numLeaves),
TreeBuilder.KW_BRANCHING_DEGREE: str(branching),
TreeBuilder.KW_NUM_INNER_NODES: str(numInnerNodes),
TreeBuilder.KW_SUPPORTED_NODE_TYPES: loggerNodeTypes}
# Instantiate a concrete GraphBuilder. Note that the
# generateNewGraph() method of this class returns a
# new, randomly generated graph that (more or less)
# satisfies all the parameters provided to the
# constructor, viz. tree_kwargs in the present case.
simpleTreeBuilder = TreeBuilder(**tree_kwargs)
# Instantiate a concrete behavior generator. Some
# behavior generators do not print unique session ID
# for each run, but it's nice to have those.
exBehavior = MonospaceInterleaving()
# Add multiple graphs to this behavior generator. The
# behaviors that it will synthesize would essentially
# be interleavings of simultaneous traversals of all
# these graphs.
for _ in range(4):
# Add 4 graphs to the behavior
exBehavior.addGraph(simpleTreeBuilder.generateNewGraph())
# Specify how many behaviors are to be synthesized,
# and get going.
wSessionID: bool = True
numTraversalsOfEachGraph: int = 2
for logLine in exBehavior.synthesize(numTraversalsOfEachGraph, wSessionID):
print(logLine)
return
In order to generate behaviors from a directed cyclic CFG, create a DCG as shown
in ./examples/03_generateControlFlowDCG.py and then generate behaviors after
adding the DCG to a behavior object as shown in the code snippet above.
Note: When generating a behavior, i.e. when traversing a graph, successors
of nodes are chosen based on the probability distributions associated with those
nodes. Different nodes rely on different distributions and these nodes are
randomly assigned in the graphs that are constructed by generateNewGraph()
methods, resulting in graphs with a mix of nodes.
Release Notes
Note: This tool is still in alpha stage, so backward compatibility is not
guaranteed between releases. However, inasmuch as users stick to graph builders'
generateNewGraph() methods, they will stay away from compatibility problems.
Major changes in v0.1.0
- Repo revival and modernization: packaging migrated from
setup.pytopyproject.toml(hatchling), dependency management viauv,rufffor linting/formatting,mypyfor type checking,pytestfor tests, GitHub Actions for CI, and a Trusted Publishing (OIDC) release flow to PyPI -- replacing the old, manualtwine uploadprocess. - Dropped support for
Python < 3.10.Python 3.10-3.13are tested in CI. - Merged in previously unreleased work from the
developbranch: a newMonospaceSimplebehavior class, and thewithSessionIDflag moved fromMonospaceInterleaving's constructor to itssynthesize()method (breaking change for any existing callers ofMonospaceInterleaving.__init__). - Dropped the unused
numpydependency;scipyis now the only runtime dependency.
Major changes in v0.0.2
- Added new graph builders, viz.
DAGBuilderandDCGBuilder, which build CFGs with skip-level edges and loops respectively. - Added new node, viz.
BinomialNode, which exploits the binomial distribution in order to select its successors at the time of graph traversal. - Added a separate utility class called
Utilsinabsynthe.cfg.utils.pyto create a newNodeobject from any of the concrete implementations ofNodeat random. All concrete implementations ofNodetherefore transparently available to graph builders (and everyone else) through this utility.
Coming up in future releases
- Sophisticated interleaving behaviors
- Logger nodes that emit more life like log messages
- Anomalous behaviors
Metadata
Release files for absynthe 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| absynthe-0.1.0.tar.gz | 22.4 kB | With provenance | Details for absynthe-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| absynthe-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for absynthe-0.1.0-py3-none-any.whl |
Total release size: 45.6 kB
Release files / absynthe-0.1.0.tar.gz
| Download URL | absynthe-0.1.0.tar.gz |
|---|---|
| Size | 22.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f06d674478a7869937c2018dcfdf51be7974cb5746db0df0582dfe55e2c732c
|
|
BLAKE2b-256 checksum How to use checksums |
7766df46e96f79ba59ce0aa0eb12fb9dcf107e96e9bfd416aab61dc01c3b6806
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 14, 2026.
Transparency logRelease files / absynthe-0.1.0-py3-none-any.whl
| Download URL | absynthe-0.1.0-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c79e15b962f7e355b277e04e7c64cdbe28e0d2d5778241663ff87d4e4fbd6ee
|
|
BLAKE2b-256 checksum How to use checksums |
315317a75b07a25f7f80e6ba1bfde0647260f5e17f049826be78559e10bb124f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 14, 2026.
Transparency logSecurity for absynthe 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for absynthe-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.