New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NetdataForAtlassian #3057
Comments
plugin uses
So |
Thanks for the thoughtful feedback. FWIW: This is not part of the Netdata project, just a blog I maintain. I have added your comments to a new 'Feedback' section: https://bitbucket.org/wkennedy/netdataforatlassian/wiki/Feedback%20and%20Followup |
btw, you may be interested for this: https://github.com/firehol/netdata/wiki/Custom-Dashboard-with-Confluence |
@ktsaou Can this be closed? |
Yes, I think it can. |
@wjkennedy I think you are the author of https://bitbucket.org/wkennedy/netdataforatlassian/wiki/Home
I run jira and I monitor it with netdata, so I have a few suggestions to make for your wiki:
Enable systemd services monitoring for debian: https://github.com/firehol/netdata/wiki/monitoring-systemd-services#how-to-enable-cgroup-accounting-on-systemd-systems-that-is-by-default-disabled
Add Atlassian applications for apps.plugin. Now your wiki provides screenshots for java applications. You can add all Atlassian apps at
/etc/netdata/apps_groups.conf
. On my system I have these (add them beforejava
):If we add such patterns, netdata will be able to provide separate chart dimensions for each of the atlassian apps, even when they run on the same server (without these patterns, netdata will group them together as
java
).access.log
file, which was automatically picked up by netdata and allowed me to have charts like these:The best part is that I can get jira API timings:
and with a bit of netdata customization, I can get a real-time view of which jira API methods are called:
For this customization I edited
/etc/netdata/python.d/web_log.conf
, removed the default jobs and added this one:It would be best if we could have an official list of all the interesting jira patterns.
The text was updated successfully, but these errors were encountered: