Skip to content

quickstart: assumes implicit knowledge of Makefile conventions #9

@lucab

Description

@lucab

First of all, thanks for the project and the docs!

Starting from no knowledge about monitoring mixins, I was trying to write some quick dashboarding mixin for a project of mine, by following the docs in this repo (as mirrored on https://monitoring.mixins.dev/).

I somehow got stuck on the step where it runs make. This assumes that the mixin-author already has a lot of knowledge about what they are supposed to do and what are the conventions around such Makefile.

I unfortunately had neither of those, so I was really tempted to just blindly copy the magic incantation from the first Makefile I could find (e.g. the node-exporter one).

I wasn't really convinced by that, and I ended up just running a minimal mixtool generate which seems to take care of the same logic.

For newcomers like me, it would be great to write down what is the interface for properly performing artifacts generations (and how to lay the mixins on disk so that generators are happy).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions