Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Every call to the 1Password Events API must be authorized with a bearer token. You must include your bearer token in the collector configuration.

For example:

Authentication method

Details

token

You will need your token to connect to the base_url.

Vendor setup

Before you can use the 1Password Events API, you'll need to:

...

Devo categorization and destination

Please check the section Data Source Description to learn about the target tables for each service.

...

This collector has different security layers that detect both an invalid configuration and abnormal operation. This table will help you detect and resolve the most common errors.

Configuration errors

Error type

Error ID

Error message

Cause

Solution

InitVariablesError

1

The parameter configuration is missing and it is mandatory

The parameter is missing in the configuration

Check the documentation and update the configuration accordingly

InitVariablesError

2

The parameter setting must be a valid instance of <type_A> not <type_B>

The parameter type in the configuration is incorrect

Check the documentation and update the configuration accordingly

InitVariablesError

3

The parameter setting must not be an empty string

The parameter is present in the configuration but it is empty

Check the documentation and update the configuration accordingly

PrePullError

200

<Variable_text>

Some errors happened when accessing the persistence

Contact Devo Support

Error

4xx-5xx

The execution of the 1Password request is having an unexpected response

Some errors happened when accessing the 1Password API

Usually, this error gets fixed in the next iteration. If it is a repeating error, please get in touch with Devo Support

Collector operations

Verify collector operations

...

The Integrations Factory Collector SDK has 3 different sender services depending on the event type to deliver (internal, standard, and lookup). This collector uses the following Sender Services:

Logging trace

Description

Number of available senders: 1

Displays the number of concurrent senders available for the given Sender Service.

Sender manager internal queue size: 0

Displays the items available in the internal sender queue.

This value helps detect bottlenecks and needs to increase the performance of data delivery to Devo. This last can be made by increasing the concurrent senders.

Total number of messages sent: 44, messages sent since "2022-06-28 10:39:22.511671+00:00": 21 (elapsed 0.007 seconds)

Displays the number of events from the last time the collector executed the pull logic. Following the given example, the following conclusions can be obtained:

  • 44 events were sent to Devo since the collector started.

  • The last checkpoint timestamp was 2022-06-28 10:39:22.511671+00:00.

  • 21 events were sent to Devo between the last UTC checkpoint and now.

  • Those 21 events required 0.007 seconds to be delivered.

By default, these traces will be shown every 10 minutes.

Sender statistics

Each service displays its performance statistics that allow checking how many events have been delivered to Devo by type:

Logging trace

Description

Number of available senders: 1

Displays the number of concurrent senders available for the given Sender Service.

Sender manager internal queue size: 0

Displays the items available in the internal sender queue.

Standard - Total number of messages sent: 57, messages sent since "2023-01-10 16:09:16.116750+00:00": 0 (elapsed 0.000 seconds

Displays the number of events from the last time the collector executed the pull logic. Following the given example, the following conclusions can be obtained:

  • 57 events were sent to Devo since the collector started.

  • The last checkpoint timestamp was 2023-01-10 16:09:16.116750+00:00.

  • 0 events were sent to Devo between the last UTC checkpoint and now.

  • Those 0 events required 0.00 seconds to be delivered.

Check memory usage

To check the memory usage of this collector, look for the following log records in the collector which are displayed every 5 minutes by default, always after running the memory-free process.

...

Code Block
  INFO InputProcess::MainThread -> [GC] global: 20.4% -> 20.4%, process: RSS(34.50MiB -> 34.08MiB), VMS(410.52MiB -> 410.02MiB)
  INFO OutputProcess::MainThread -> [GC] global: 20.4% -> 20.4%, process: RSS(28.41MiB -> 28.41MiB), VMS(705.28MiB -> 705.28MiB)

Change log

Release

Released on

Release type

Details

Recommendations

v1.1.0

2024-08-30

Status
colourGreen
titleIMPROVEMENTS

  • Updated DC SDK to v1.12.4

  • Upgraded Docker Base image to 1.3.0.

Recommended version

v1.0.1

2023-11-08

Status
colourGreen
titleIMPROVEMENTS

  • Update default tag for audit logs

Upgrade

v1.0.0

2023-11-01

Status
colourGreen
titleIMPROVEMENTS

  • Updated DCSDK from 1.4.1 to 1.9.2:

  • Upgrade internal dependencies

  • Store lookup instances into DevoSender to avoid creation of new instances for the same lookup

  • Ensure service_config is a dict into templates

  • Ensure special characters are properly sent to the platform

  • Changed log level to some messages from info to debug

  • Changed some wrong log messages

  • Upgraded some internal dependencies

  • Changed queue passed to setup instance constructor

  • Ability to validate collector setup and exit without pulling any data

  • Ability to store in the persistence the messages that couldn't be sent after the collector stopped

  • Ability to send messages from the persistence when the collector starts and before the puller begins working

  • Ensure special characters are properly sent to the platform

  • Added a lock to enhance sender object

  • Added new class attrs to the setstate and getstate queue methods

  • Fix sending attribute value to the setstate and getstate queue methods

  • Added log traces when queues are full and have to wait

  • Added log traces of queues time waiting every minute in debug mode

  • Added method to calculate queue size in bytes

  • Block incoming events in queues when there are no space left

  • Send telemetry events to Devo platform

  • Upgraded internal Python dependency Redis to v4.5.4

  • Upgraded internal Python dependency DevoSDK to v5.1.3

  • Fixed obfuscation not working when messages are sent from templates d

  • New method to figure out if a puller thread is stopping

  • Upgraded internal Python dependency DevoSDK to v5.0.6

  • Improved logging on messages/bytes sent to Devo platform

  • Fixed wrong bytes size calculation for queues

  • New functionality to count bytes sent to Devo Platform (shown in console log)

  • Upgraded internal Python dependency DevoSDK to v5.0.4

  • Fixed bug in persistence management process, related to persistence reset

  • Aligned source code typing to be aligned with Python 3.9.x

  • Inject environment property from user config

  • Obfuscation service can be now configured from user config and module definiton

  • Obfuscation service can now obfuscate items inside arrays

Upgrade

v0.1.2

2023-01-18

Status
colourGreen
titleIMPROVEMENTS

Added

  • More log traces related to execution environment details

  • Global rate limiters functionality

  • Extra checks for supporting MacOS as a development environment

  • Obfuscation functionality

Changed

  • Some log traces now are shown less frequently

  • The default value for the logging frequency for "main" processes has been changed (to 120 seconds)

  • Updated some Python Packages

  • Controlled stopping functionality more stable when using the "template"

  • Improved some log messages related to Devo certificates (when using the Devo sender)

  • Validate JSON objects before saving them to persistence (using the filesystem)

Upgrade

Change log

...

Release

...

Released on

...

Release type

...

Details

...

Recommendations

...

v1.0.1

...

...

Status
colourGreen
titleV1

...

Release Version

...

Recommended version

...

v1.0.0

...

...

Status
colourGreen
titleV1

...

Release Version

...

Recommended version