huuancao / sentinel Goto Github PK

Create readme with build instructions and useful beacons, e.g. travis build state, test coverage, godoc, go report.

Add beacon in readme showing the test coverage. The service is free for open source projects.
Few years back I used https://docs.coveralls.io/go, but there are other tools.

Add sonarqube, the service is also free for open source projects.

At this point, we could make a basic monitoring subcommand with any APIs and check the health:

• Logstash
• Elasticsearch
• Filebeat
• etc

Not really a revolution but whatever... We could expose the metrics with Prometheus too ¯_(ツ)_/¯

I do not really see another way than brute-force for this one...

Add version command that return the version, git commit, goversion with which the executable was build.

Would be nice to add some Kafka monitoring features:

• Topic monitoring
• Consumer lag monitoring

Add commands to:

• create topics
• update topics
• create acls
• update acls

Jesus Christ, I will handle this in this issue and not in #1 ...

Just for the giggle, setup Travis for building.
@johandroz You wanted to do a Makefile maybe you want to look into this?
https://docs.travis-ci.com/user/customizing-the-build/

This is just an idea.

Add a logger for debugging purpose...

First idea of the tool:

1. Enumerate all sub-domains of a given domain
2. check the validity of their certificate

For (1), brute-force is definitely out of question, their are a few third-party tools out there.
A few ideas here: https://blog.appsecco.com/a-penetration-testers-guide-to-sub-domain-enumeration-7d842d5570f6