sumologic-gsuitealertcenter
Solution to pull alerts from G Suite Alert Center to Sumo Logic
Installation
This collector can be deployed both onprem and on cloud(google cloud functions). For installing the collector as a serverless solution refer these docs
Deploying the collector on a VM
-
Setup the Alert Center API by referring to the following docs. Here while creating key in service account make a note of the location of Service Account JSON file that has been downloaded in your computer you will need it later.
-
Add a Hosted Collector and HTTP Source
- To create a new Sumo Logic Hosted Collector, perform the steps in Configure a Hosted Collector.
- Add an HTTP Logs and Metrics Source. Under Advanced you'll see options regarding timestamps and time zones and when you select Timestamp parsing specify the custom time stamp format as shown below:
- Format:
yyyy-MM-dd'T'HH:mm:ss.SSS'Z' - Timestamp locator:
\"createTime\": (.*),.
- Format:
-
Configuring the sumologic-gsuitealertcenter collector
Below instructions assume pip is already installed if not then, see the pip docs on how to download and install pip. sumologic-gsuitealertcenter is compatible with python 3.7 and python 2.7. It has been tested on Ubuntu 18.04 LTS and Debian 4.9.130. Login to a Linux machine and download and follow the below steps:
-
Install the collector using below command
pip install sumologic-gsuitealertcenter -
Create a configuration file named gsuitealertcenter.yaml in home directory by copying the below snippet. Add the SUMO_ENDPOINT, CREDENTIALS_FILEPATH(downloaded in step 1) and DELEGATED_EMAIL parameters obtained from step 1 and step 2 and save it.
SumoLogic: SUMO_ENDPOINT: <SUMO LOGIC HTTP URL> GsuiteAlertCenter: DELEGATED_EMAIL: "<use the default email address>" CREDENTIALS_FILEPATH: "<path to json Service Accouont JSON file>" Collection: ENVIRONMENT: onprem -
Create a cron job for running the collector every 5 minutes by using the crontab -e and adding the below line
*/5 * * * * /usr/bin/python -m sumogsuitealertscollector.main > /dev/null 2>&1
-
Metadata
Release files for sumologic-gsuitealertcenter 1.0.6
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 |
|---|---|---|---|---|
| sumologic-gsuitealertcenter-1.0.6.tar.gz | 21.1 kB | Without provenance | Details for sumologic-gsuitealertcenter-1.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sumologic_gsuitealertcenter-1.0.6-py3-none-any.whl | Python 3 | none | any | Details for sumologic_gsuitealertcenter-1.0.6-py3-none-any.whl |
Total release size: 48.9 kB
Release files / sumologic-gsuitealertcenter-1.0.6.tar.gz
| Download URL | sumologic-gsuitealertcenter-1.0.6.tar.gz |
|---|---|
| Size | 21.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f282dce8c8f40dd8617e57af88dd21020c39cc4d6cb274524c2ae6855db4cb57
|
|
BLAKE2b-256 checksum How to use checksums |
661b0b740223b85c4e34d9ecbc0ad3292d4c1eedc271c74825cc86cc454c9ecd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.0
|
Release files / sumologic_gsuitealertcenter-1.0.6-py3-none-any.whl
| Download URL | sumologic_gsuitealertcenter-1.0.6-py3-none-any.whl |
|---|---|
| Size | 27.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f7cf0b8de0e7106d3813ecdafbc6cdd72bfefe55d5d27d6443055e04c0db600
|
|
BLAKE2b-256 checksum How to use checksums |
b04e47f6c5086400a6b1c1b7ebdca33020156a572c29385793477d83fe1b5720
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.0
|
Security for sumologic-gsuitealertcenter 1.0.6
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.