Documentation¶
Important
Features marked with “Experimental” can change or disappear without warning, do not use them in production.
- Quick Reference
- Project kickstart
- Building blocks
- Data Transformation Language (DTL)
- Data management
- Data synchronization
- Connectors
- The Connector Contract
- Configuring connectors
- Patterns
- Authentication schemes
- Combine all and webhook events
- Continuation
- Datatype naming
- Datatypes should follow the API
- Datatypes with lists of linked objects
- Duplicate hops block
- Connector asymmetry
- Open to extension closed for modification
- Pagination
- Parameterized datatypes
- Receiving webhook events
- Registering webhooks
- Share template extension points
- Single share
- Two step collect
- Use datatype specific system operations
- Use connector templates
- Deletion tracking of webhook events
- Operations
- Security
- Metrics and monitoring
- Pump Execution Dataset
- Configuration Management
- Self-hosted service
- Self-hosted on Kubernetes
- Debugging
- Changing the loglevel via the “/api/logs” api endpoint
- Profiling all Sesam API calls
- Profiling one specific Sesam API call
- Profiling a pump run
- Using the “/api/status/stacktrace” api endpoint
- Sending the SIGUSR1 signal to the sesam node process
- Checking if the health-checker thread in the node has created a stacktrace
- Using the “Instance configuration” gui
- Upload a full node-config with a node metadata entity
- Writing a “/sesam/node/data/startup_options.json” file
- /api/status/heap
- /api/status
- /api/status/debugmallocstats
- Behind the scenes
- Troubleshooting
- Data platforms
- Tools
- Service Configuration
- Service API
- Deprecated features