Skip to content
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

NEW: Energi Core daemon monitoring, suits other Bitcoin forks #5894

Merged
merged 14 commits into from Apr 27, 2019

Conversation

andvgal
Copy link
Contributor

@andvgal andvgal commented Apr 18, 2019

Summary

Adds monitoring of Energi Core Bitcoin-derived daemon monitoring. It is named after the contributing cryptocurrency team, but targets a wide range of projects.

As there is no strict RPC standardization, there is no 100% guarantee that it will work with other forks of Bitcoin. Although, most of them should be supported and can be used with this plugin.

Component Name

New Python collector module.

Additional Information

Smoke tested with make dist.

Depends on #5893
Ignore UrlService changed here.

@andvgal
Copy link
Contributor Author

andvgal commented Apr 18, 2019

@Ferroin It is part of energid.conf, but OK. It can be added there.

Maybe you know how to run Codacy Markdown checks locally then?

@Ferroin
Copy link
Member

Ferroin commented Apr 18, 2019

Regarding the Codacy checks, I'm not sure of any way to run them locally, but in this case the only issue I see is the indentation of the nested list items (Markdown technically requires two or more spaces of indentation for each nesting level), so just fixing that should clear up the checks. My suggestion would be to just use 4 spaces there instead of 2 like Codacy is suggesting, as that will make it consistent with the other documentation.

@andvgal
Copy link
Contributor Author

andvgal commented Apr 18, 2019

Well, it was 4 spaces originally, but Codacy did not like that either.

Tried to copy list style from other modules. Could it be they are just broken and not shown in PR checks...?

@andvgal
Copy link
Contributor Author

andvgal commented Apr 18, 2019

That's interesting. Without any changes to the Markdown list, Codacy accepted it from the third time,

@Ferroin
Copy link
Member

Ferroin commented Apr 18, 2019

Well, it was 4 spaces originally, but Codacy did not like that either.

That's interesting. Without any changes to the Markdown list, Codacy accepted it from the third time,

Sounds like a bug on Codacy's side to me.

collectors/python.d.plugin/energid/energid.chart.py Outdated Show resolved Hide resolved
collectors/python.d.plugin/energid/energid.chart.py Outdated Show resolved Hide resolved
collectors/python.d.plugin/energid/energid.chart.py Outdated Show resolved Hide resolved
collectors/python.d.plugin/energid/energid.chart.py Outdated Show resolved Hide resolved
@netdatabot netdatabot added area/collectors Everything related to data collection area/docs area/external/python labels Apr 18, 2019
@andvgal andvgal changed the title NEW: Energi Core daemon monitoring, suites other Bitcoin forks NEW: Energi Core daemon monitoring, suits other Bitcoin forks Apr 18, 2019
@andvgal
Copy link
Contributor Author

andvgal commented Apr 18, 2019

Well, Codacy markdown behaves strange...

@andvgal
Copy link
Contributor Author

andvgal commented Apr 18, 2019

Codacy is passed, but it shows "changes requested" with no obvious items left.

ilyam8
ilyam8 previously approved these changes Apr 18, 2019
ilyam8
ilyam8 previously approved these changes Apr 19, 2019
@andvgal
Copy link
Contributor Author

andvgal commented Apr 19, 2019

Yeah... It seems Codacy Markdown got conquered. Looks like, the root cause of tons of misleading errors was broken bold notation in one of the list items.

EDIT: no, it also a very strange behavior. It shows "Passed" and then changes to fail after some time.

@andvgal
Copy link
Contributor Author

andvgal commented Apr 19, 2019

OK, it was absolutely not obvious and many other READMEs fail Markdown check.

I'll submit a separate PR with remark-lint installed.

@andvgal
Copy link
Contributor Author

andvgal commented Apr 19, 2019

OK...

  1. Codacy integration has some flaws - it incorrectly reflects status in GitHub during processing.
  2. The correct remark-lint config seems to be here: https://github.com/codacy/codacy-remark-lint/raw/master/.remarkrc.js
    • However, English text processing has to be disabled locally.

Copy link
Contributor

@paulkatsoulakis paulkatsoulakis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM -- tested in detail by @andvgal

@ilyam8 ilyam8 merged commit 0252ce3 into netdata:master Apr 27, 2019
@ilyam8
Copy link
Member

ilyam8 commented Apr 27, 2019

thanks @andvgal !

thiagoftsm pushed a commit to thiagoftsm/netdata that referenced this pull request May 5, 2019
…a#5894)

* NEW: Energi Core daemon monitoring, suites other Bitcoin forks

* Attempt to make Codacy checks happy

* Added energid sample configuration, enabled by default

* Post-review fixes & revised charts

* Added default Energi, Bitcoin and Dash to energid.conf configuration

* Fighting with Codacy markdown check

* Added energid protocol description comment

* Added JSON_RPC_VERSION as module variable

* Screw you Codacy markdown

* Screw you Codacy Markdown #2

* Screw you Codacy Markdown #3

* Finally, fixed what remark-lint wants

* Strict local remark-lint + plugins pass for README.md

* Attempt with another remark-lint configuration
jackyhuang85 pushed a commit to jackyhuang85/netdata that referenced this pull request Jan 1, 2020
…a#5894)

* NEW: Energi Core daemon monitoring, suites other Bitcoin forks

* Attempt to make Codacy checks happy

* Added energid sample configuration, enabled by default

* Post-review fixes & revised charts

* Added default Energi, Bitcoin and Dash to energid.conf configuration

* Fighting with Codacy markdown check

* Added energid protocol description comment

* Added JSON_RPC_VERSION as module variable

* Screw you Codacy markdown

* Screw you Codacy Markdown netdata#2

* Screw you Codacy Markdown netdata#3

* Finally, fixed what remark-lint wants

* Strict local remark-lint + plugins pass for README.md

* Attempt with another remark-lint configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/collectors Everything related to data collection area/docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants