catalogstatediscoveraboutstream-mapsschema-flatteningbatch
Settings
| Setting | Required | Default | Description |
|---|---|---|---|
| token | True | None | API Token for Better Stack |
| start_date | False | None | Earliest datetime to get data from |
| stream_maps | False | None | Config object for stream maps capability. For more information check out Stream Maps. |
| stream_map_config | False | None | User-defined config values to be used within map expressions. |
| flattening_enabled | False | None | 'True' to enable schema flattening and automatically expand nested properties. |
| flattening_max_depth | False | None | The max depth to flatten schemas. |
| batch_config | False | None |
A full list of supported settings and capabilities is available by running: tap-betterstack --about
Streams
Supported
monitorsmonitor_groupsheartbeatsheartbeat_groupson_callsescalation_policiesincidentsincident_eventsemail_integrationsincoming_webhooksstatus_pages
Planned (PRs welcome!)
Usage
You can easily run tap-betterstack by itself or in a pipeline using Meltano.
Executing the Tap Directly
tap-betterstack --version
tap-betterstack --help
tap-betterstack --config CONFIG --discover > ./catalog.json
Developer Resources
-
Developer TODO:As a first step, scan the entire project for the text "TODO:" and complete any recommended steps, deleting the "TODO" references once completed.
Initialize your Development Environment
curl -LsSf https://astral.sh/uv/install.sh | sh # or see https://docs.astral.sh/uv/getting-started/installation/
uv sync
Create and Run Tests
Create tests within the tests subfolder and then run:
uv run pytest
You can also test the tap-betterstack CLI interface directly using the virtual environment:
uv run tap-betterstack --help
Testing with Meltano
Note: This tap will work in any Singer environment and does not require Meltano. Examples here are for convenience and to streamline end-to-end orchestration scenarios.
Use Meltano to run an EL pipeline:
uvx meltano invoke tap-betterstack --version
uvx meltano run tap-betterstack target-jsonl
SDK Dev Guide
See the dev guide for more instructions on how to use the SDK to develop your own taps and targets.
Metadata
Release files for tap-betterstack 0.4.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 | |
|---|---|---|---|
| tap_betterstack-0.4.0.tar.gz | 75.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tap_betterstack-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 87.7 kB
Release files / tap_betterstack-0.4.0.tar.gz
| Download URL | tap_betterstack-0.4.0.tar.gz |
|---|---|
| Size | 75.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d934c97bf1ea088c4a379328071564df75faf9c1e8bbb96fc72909a1cb44e222
|
|
BLAKE2b-256 checksum How to use checksums |
401190701ba0386cd8c423af5b603b143d87bc1a6a578d339be3449c2db1bdc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 31, 2026.
Transparency logRelease files / tap_betterstack-0.4.0-py3-none-any.whl
| Download URL | tap_betterstack-0.4.0-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38346a246c34a132dc36685304b6762bb0d524480c45b611edb2e69e7ddd3138
|
|
BLAKE2b-256 checksum How to use checksums |
bcb042ab89464d52c74977027af68121139d776059ee8cdbd996dd3e82dc0a5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 31, 2026.
Transparency log
