monitoring of webhooks parameters

[Artem Semenov]

Hello!

Interested in the following parameters: atlassian.webhooks.search.default.limit webhooks.executor.queue.size perhaps there is a working practice on how to do this through the Prometheus Exporter for Jira plugin or something else?

After the introduction of asynchronous webhooks, there was a shortage of webhooks.search.default.limit, increasing this parameter solved the problem, but there is a need to monitor this parameter to make sure that this parameter is exceeded.

[Benjamin]

HI @Artem Semenov ,

Not sure if you can monitor it unless it shows up in the log. Like any performance parameter, I would do so with caution to understand why my system is at this state. Is it something that part of the way the system has schedule due the actual working activity? or is it some automation or triggers that running but doesn't need to be? Usually, the default parameters covers majority of cases in my experience. Often times, it's a matter of maintenance and clean up what's unecessary.

-Ben

[Artem Semenov]

Hi,

We use various plug-ins and also a sufficient number of configured webhooks for events (update, workflow, etc.) in projects that are transferred to other services, which is why there were not enough standard limits.

The problem was identified in the logs only when the debug mode for webhooks was enabled.

Therefore, the question arose whether it is possible to monitor these?