It is a helper tool for Azure Monitor. It is not official. Recently it is used the term Azure Monitor logs instead of Log Analytics. Log data is still stored in a Log Analytics workspace and is still collected and analyzed by the same Log Analytics service. https://docs.microsoft.com/en-us/azure/azure-monitor/
Install
pip install azmonitor
Example
import azmonitor
log_type = 'AzMonitor'
customer_id = 'xxxxx-xxxx-xxxx-xxxx-xxxxx'
shared_key = 'xxxxxxxxxxxxxxxxxxxxxxxxxx'
applog = azmonitor.LogAnalytics(log_type, customer_id, shared_key)
# Single Data
data = {'status': 'starting', 'value': 50}
applog.log(data)
# Multi Data
list_data = []
for i in range(3):
list_data.append({'status': 'starting', 'value': i})
applog.logs(list_data)
Metadata
Release files for azmonitor 0.8.1
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 |
|---|---|---|---|---|
| azmonitor-0.8.1.tar.gz | 2.6 kB | Without provenance | Details for azmonitor-0.8.1.tar.gz |
Release files / azmonitor-0.8.1.tar.gz
| Download URL | azmonitor-0.8.1.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
57456cf2865f0636f5132a9cfe425dece966ea24e36f6598b2800a0be1cc913e
|
|
BLAKE2b-256 checksum How to use checksums |
a93857cddabcf16d7151929262c146d08baf30f1e43146fbba07f63587b5c360
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.9.1 tqdm/4.28.1 CPython/3.7.1
|
Security for azmonitor 0.8.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.