Skip to main content

master Build Status LICENSE

wheel version python

Devo Python SDK

This is the SDK to access Devo directly from Python. It can be used to:

  • Send events and files to Devo.
  • Make queries.
  • Manage deferred tasks.

Requirements

The Devo SDK for Python requires Python 2.7+ or Python 3.4+

Quick Start

Installing the SDK

You can install the Devo SDK by using easy_install or pip:

#option 1
easy_install devo-sdk

#option 2
pip install devo-sdk

You can use sources files, clonning the project too:

#option 3
python setup.py install

#option 4
pip install .

#option 5 - dev option
pip install -e .

Documentation

You has specific documentation in docs folder for each part of SDK:

Contributing

See PyLibs contributing guide.
Pull and merge requests are welcome ☺

Endpoints

Sender

To send data with Devo SDK, first choose the required endpoint depending on the region your are accessing from:

  • USA: us.elb.relay.logtrust.net:443
  • EU: eu.elb.relay.logtrust.net:443

You have more information in the official documentation of Devo, Sending data to Devo.

API

To perform a request with API, first choose the required endpoint depending on the region your are accessing from:

You have more information in the official documentation of Devo, REST API v2 .

Credentials

To obtain the access credentials necessary to use this SDK, you must have an account in DEVO.
Check the security credentials info for more details.

Certificates

You need use a three files (Cert, key and chain) to secure send data to Devo. Administrator users can find them in AdministrationCredentials, in the X.509 tab.

API authorization

You can use a domain API key and API secret to sign the request. These are are a pair of credentials that every Devo account owns. Administrator users can find them in AdministrationCredentials, in the Access Keys tab.

Launch tests

run_tests script

You can run tests from the main folder of SDK To launch this script, you need either the environment variables loaded in the system, or the environment.env file in the root of the SDK with the correct values, since to test all the SDK functionalities it is necessary to connect to Devo for the tests of sending and extracting data. You has a example file called environment.env.example

Its normal, by the way, TCP tests fails in clients or not Devo developers systems.

~/projects/devo-python-sdk > python setup.py test 
~/projects/devo-python-sdk > python run_tests.py

You can add option "Coverage" for create HTML report about tests.

~/projects/devo-python-sdk > python run_tests.py --coverage

Run using Unittest command

You can see references in unittest documentation

For commands like:

python -m unittest discover -p "*.py" 

If you launch this command from the root directory of the SDK, you need to have the environment variables in your system for all the tests that require connection to Devo can work, not being able to use the environment.env file as in the script.

Contact Us

You can contact with us at support@devo.com.

License

MIT License

(C) 2018 Devo, Inc.

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.

Release files for devo-sdk 2.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for devo-sdk 2.1.0
File Size Uploaded
devo-sdk-2.1.0.tar.gz 31.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for devo-sdk 2.1.0
File Interpreter ABI Platform
devo_sdk-2.1.0-py2.py3-none-any.whl Python 2, Python 3 none any Details

Total release size: 70.8 kB

Release files / devo-sdk-2.1.0.tar.gz

Download URL devo-sdk-2.1.0.tar.gz
Size 31.7 kB
Tags Source
SHA-256 checksum
How to use checksums
f664ed696eee8ffb2aa41a3166273265f41eb7f9c11fc60d73cc1db88ad0f120
BLAKE2b-256 checksum
How to use checksums
d591f50888a3c3b50a570890ffe183b005e024084e3a7844550f7ec0f5ca5e5b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.5.6

Release files / devo_sdk-2.1.0-py2.py3-none-any.whl

Download URL devo_sdk-2.1.0-py2.py3-none-any.whl
Size 39.1 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
db208add68be8a57f7f127ea65579444ea2bec850a48f5b01c3ea53212c704f1
BLAKE2b-256 checksum
How to use checksums
a7103dfdd0890864c4edf52c126e181b5e623226049d86077a0bbf08d607b349
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.5.6

Release history Release notifications | RSS feed

7.0.2

2 release files

7.0.1

2 release files

7.0.0

2 release files

6.0.7

2 release files

6.0.6

2 release files

6.0.5

2 release files

6.0.4

2 release files

6.0.3

2 release files

6.0.2

2 release files

6.0.1

2 release files

6.0.0

2 release files

5.4.1

2 release files

5.4.0

2 release files

5.3.0

2 release files

5.2.0

2 release files

5.1.10

2 release files

5.1.9

2 release files

5.1.8

2 release files

5.1.7

2 release files

5.1.6

2 release files

5.1.5

2 release files

5.1.4

2 release files

5.1.3

2 release files

5.1.1

2 release files

5.1.0

2 release files

5.0.6

2 release files

5.0.5

2 release files

5.0.4

2 release files

5.0.2

2 release files

4.0.3

2 release files

4.0.2

2 release files

4.0.1

2 release files

4.0.0

2 release files

3.6.7

2 release files

3.6.4

2 release files

3.6.3

2 release files

3.6.2

2 release files

3.6.1

2 release files

3.5.0

2 release files

3.4.2

2 release files

3.4.1

2 release files

3.3.7

2 release files

3.3.6

2 release files

3.3.3

2 release files

3.3.2

2 release files

3.3.1

2 release files

3.3.0

2 release files

3.2.5

2 release files

3.2.2

2 release files

3.2.1

2 release files

3.2.0

2 release files

3.1.1

2 release files

3.1.0

2 release files

3.0.3

2 release files

2.2.4

2 release files

2.2.3

2 release files

2.2.1

2 release files

2.2.0

2 release files

2.1.2

2 release files

2.1.1

2 release files

This release

2.1.0 This release

2 release files

2.0.2

2 release files

2.0.0

2 release files

1.6.3

2 release files

1.6.1

2 release files

1.6.0

2 release files

1.5.2

2 release files

1.5.0

2 release files

1.4.0

2 release files

1.3.1

2 release files

1.3.0

2 release files

1.2.1

2 release files

1.2.0

2 release files

1.1.4

2 release files

1.1.3

2 release files

1.1.2

2 release files

1.1.1

2 release files

1.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page