We believe building some types of software are not trivial and when there are many applications, it is a good thing to make sure you have some consistency around certain pieces of software. Primarily that logging follows a very strict convention for your organization or project. So having some analysis across all your systems would be a good thing. That is how this started.
We need a way to check on what log categories we have, and how well our structured (or lack of following the structured format) was occuring across our entire code base.
I would like different information about Mule code. What http:request does not have a Content-Type or User-Agent defined? What logger’s do not have a category or “transactionId” in the message? What flows are sync or async? I’m thinking more information about the code base. A static analysis.
Such as find regex within loggers message attribute (or category attribute)
Or does does attribute X have values within this acceptable list?
We also come across where certain elements needed to configured a certain way, and often devs, by mistake or otherwise, would change these attributes. So this is intended to provide that safety net, that what we end up deploying out satisfies a certain criteria.
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
What things you need to install the software and how to install them
Give examples
A step by step series of examples that tell you have to get a development env running
Say what the step will be
Give the example
And repeat
until finished
End with an example of getting some data out of the system or using it for a little demo
Explain how to run the automated tests for this system
Explain what these tests test and why
Give an example
Explain what these tests test and why
Give an example
Add additional notes about how to deploy this on a live system
- Library - Some framework used
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
We use SemVer for versioning. For the versions available, see the tags on this repository.
- Chad Gorshing - Initial work - cgorshing
See also the list of contributors who participated in this project.
This project is licensed under the MIT License - see the LICENSE.md file for details
- Hat tip to anyone who's code was used
- Inspiration
- etc