Skip to content

DEBUG messages are put into the ERROR log function #46

Description

@10erika

Hello 1Password people,
a few weeks ago I deployed your app and I must say, it's a really cool one, the documentation is nicely detailed, I'm really impressed. 😄

I configured everything and it runs perfectly, however, when I search for the _internal index, I see ~1000 in the error logs every hour, which show debug messages that only say that the app made a POST request to the 1Password endpoint.

Here are a few examples of those "error" messages:

07-23-2024 08:22:46.295 +0000 ERROR ExecProcessor [3049 ExecProcessor] - message from "/opt/splunk/etc/apps/onepassword_events_api/bin/audit_events" 2024/07/23 08:22:46 [DEBUG] POST https://events.1password.eu/api/v1/auditevents
07-23-2024 08:22:39.314 +0000 ERROR ExecProcessor [3049 ExecProcessor] - message from "/opt/splunk/etc/apps/onepassword_events_api/bin/item_usages" 2024/07/23 08:22:39 [DEBUG] POST https://events.1password.eu/api/v1/itemusages
07-23-2024 08:22:38.268 +0000 ERROR ExecProcessor [3049 ExecProcessor] - message from "/opt/splunk/etc/apps/onepassword_events_api/bin/signin_attempts" 2024/07/23 08:22:38 [DEBUG] POST https://events.1password.eu/api/v1/signinattempts

I know they can be ignored, but it would be useful to have the debug logs at debug level - and also being able to turn them off if they are not needed.
Is this the intended way or will be fixed in a future release? Also, is there a plan to include a function to change the logging level in the GUI?

Many thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions