datadog-async-handler 0.1.2__tar.gz

datadog_async_handler-0.1.2/.gitignore

@@ -0,0 +1,175 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be added to the global gitignore or merged into this project gitignore.  For a PyCharm
+#  project, it is recommended to create a project-specific .gitignore file and
+#  place it in the project root directory.
+.idea/
+
+# VS Code
+.vscode/
+
+# Local development
+.hatch/
+.pytest_cache/
+
+# macOS
+.DS_Store
+
+# Windows
+Thumbs.db
+ehthumbs.db
+Desktop.ini

datadog_async_handler-0.1.2/CHANGELOG.md

@@ -0,0 +1,48 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+- Initial release of datadog-http-handler
+- Asynchronous HTTP logging handler for Datadog
+- Batching support with configurable batch size and flush intervals
+- Automatic retry logic with exponential backoff
+- Comprehensive error handling and graceful degradation
+- Type hints and mypy compatibility
+- Support for all Datadog sites (US, EU, Government, etc.)
+- Environment variable configuration support
+- Framework integration examples (Django, FastAPI, Flask)
+- Background worker thread for non-blocking log processing
+- Automatic tag enrichment (environment, service, version)
+- Memory-efficient queue management
+- Graceful shutdown handling
+
+### Changed
+- N/A (initial release)
+
+### Deprecated
+- N/A (initial release)
+
+### Removed
+- N/A (initial release)
+
+### Fixed
+- N/A (initial release)
+
+### Security
+- N/A (initial release)
+
+## [0.1.0] - 2025-08-25
+
+### Added
+- Initial development version
+- Core DatadogHTTPHandler implementation
+- Basic test suite
+- Documentation and examples
+- Modern Python packaging with Hatch
+- Comprehensive development tooling (Ruff, mypy, pytest)

datadog_async_handler-0.1.2/CONTRIBUTING.md

@@ -0,0 +1,207 @@
+# Contributing to datadog-http-handler
+
+Thank you for your interest in contributing to datadog-http-handler! This document provides guidelines for contributing to the project.
+
+## Development Setup
+
+### Prerequisites
+
+- Python 3.9 or higher
+- [UV](https://github.com/astral-sh/uv) package manager
+
+### Setup
+
+1. Clone the repository:
+```bash
+git clone https://github.com/enlyft/datadog-http-handler.git
+cd datadog-http-handler
+```
+
+2. Install UV:
+```bash
+curl -LsSf https://astral.sh/uv/install.sh | sh
+```
+
+3. Install dependencies:
+```bash
+uv sync --extra dev
+```
+
+4. Install pre-commit hooks:
+```bash
+uv run pre-commit install
+```
+
+## Development Workflow
+
+### Running Tests
+
+```bash
+# Run all tests
+uv run pytest
+
+# Run with coverage
+uv run pytest --cov=src/datadog_http_handler --cov-report=term-missing
+
+# Run specific test
+uv run pytest tests/test_handler.py::TestDatadogHTTPHandler::test_init_with_api_key
+```
+
+### Code Quality
+
+```bash
+# Format code
+uv run ruff format
+
+# Lint code
+uv run ruff check
+
+# Type checking
+uv run mypy src/datadog_http_handler tests
+
+# Run all quality checks
+uv run pre-commit run --all-files
+```
+
+### Building
+
+```bash
+# Build package
+uv build
+
+# Install locally for testing
+uv pip install -e .
+```
+
+## Code Style
+
+This project uses:
+- **Ruff** for linting and formatting
+- **mypy** for type checking
+- **pytest** for testing
+
+### Code Guidelines
+
+1. **Type Hints**: All public functions and methods must have type hints
+2. **Docstrings**: All public classes and functions must have docstrings
+3. **Tests**: All new features must include tests
+4. **Coverage**: Maintain >95% test coverage
+
+### Example Function
+
+```python
+def process_log_item(record: logging.LogRecord, tags: Optional[list[str]] = None) -> HTTPLogItem:
+    """Process a log record into a Datadog HTTP log item.
+    
+    Args:
+        record: The log record to process
+        tags: Optional additional tags to include
+        
+    Returns:
+        Formatted HTTP log item ready for submission
+        
+    Raises:
+        ValueError: If record cannot be processed
+    """
+    # Implementation here
+    pass
+```
+
+## Testing
+
+### Test Structure
+
+- **Unit Tests**: Test individual functions and methods
+- **Integration Tests**: Test component interactions
+- **Performance Tests**: Benchmark critical paths
+
+### Writing Tests
+
+```python
+import pytest
+from datadog_http_handler import DatadogHTTPHandler
+
+def test_handler_initialization():
+    """Test that handler initializes correctly."""
+    handler = DatadogHTTPHandler(
+        api_key="test-key",
+        service="test-service"
+    )
+    assert handler.service == "test-service"
+    handler.close()
+```
+
+### Test Fixtures
+
+Use the provided fixtures in `tests/conftest.py`:
+
+```python
+def test_log_formatting(handler_config, sample_log_record):
+    """Test log record formatting."""
+    handler = DatadogHTTPHandler(**handler_config)
+    log_item = handler._format_log_item(sample_log_record)
+    assert log_item.service == "test-service"
+```
+
+## Documentation
+
+### Docstring Style
+
+Use Google-style docstrings:
+
+```python
+def my_function(param1: str, param2: int = 0) -> bool:
+    """Brief description of the function.
+    
+    Longer description if needed.
+    
+    Args:
+        param1: Description of param1
+        param2: Description of param2 with default value
+        
+    Returns:
+        Description of return value
+        
+    Raises:
+        ValueError: When param1 is invalid
+        ConnectionError: When network request fails
+    """
+```
+
+## Pull Request Process
+
+1. **Fork** the repository
+2. **Create** a feature branch: `git checkout -b feature/amazing-feature`
+3. **Make** your changes
+4. **Add** tests for new functionality
+5. **Run** quality checks: `uv run pre-commit run --all-files`
+6. **Commit** your changes: `git commit -m "Add amazing feature"`
+7. **Push** to your fork: `git push origin feature/amazing-feature`
+8. **Create** a Pull Request
+
+### PR Requirements
+
+- [ ] All tests pass
+- [ ] Code coverage maintained (>95%)
+- [ ] Type checking passes
+- [ ] Linting passes
+- [ ] Documentation updated
+- [ ] CHANGELOG.md updated
+
+## Release Process
+
+1. Update version in `src/datadog_http_handler/__init__.py`
+2. Update CHANGELOG.md
+3. Create a tag: `git tag v1.0.0`
+4. Push tag: `git push origin v1.0.0`
+5. GitHub Actions will automatically build and publish
+
+## Getting Help
+
+- **Issues**: Report bugs and request features on GitHub Issues
+- **Discussions**: Ask questions in GitHub Discussions
+- **Documentation**: Check the README.md and code docstrings
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the MIT License.

datadog_async_handler-0.1.2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Parth
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.