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

Allow for custom data fields in components #2226

Closed
cascer1 opened this issue Nov 1, 2016 · 4 comments
Closed

Allow for custom data fields in components #2226

cascer1 opened this issue Nov 1, 2016 · 4 comments
Labels

Comments

@cascer1
Copy link

cascer1 commented Nov 1, 2016

Hi!

I'm working on a tool that automatically checks certain things for components I added to Cachet (Right now, I'm only pinging and getting response codes).

I currently have a file that simply stores the settings for each component in an array. In this I store the url, check type, expected response code, timeout, and some other details needed for tests. I tried moving this to tags, but that didn't work because you can't have a custom tag slug (as far as I know).

I would like to be able to add custom data to a component. I imagine this being similar to tags, but instead of the tag slug being automatically generated, it is manually entered by me. That way I can store some data used by my automatic checking tool.

In the API response for GET /components/:id, I could imagine a response like

    {
        "id": 1,
        "name": "API",
        "description": "This is the Cachet API.",
        "link": "",
        "status": 1,
        "order": 0,
        "group_id": 0,
        "created_at": "2015-07-24 14:42:10",
        "updated_at": "2015-07-24 14:42:10",
        "deleted_at": null,
        "status_name": "Operational",
        "tags": [
            "slug-of-tag": "Tag Name"
        ],
        "meta": [
            "check-type": "http",
            "timeout": "15",
            "port": "80"
        ]
    }
@ConnorVG
Copy link
Contributor

ConnorVG commented Nov 1, 2016

This is quite an interesting idea.

@jbrooksuk
Copy link
Member

I like this.

Somebody feel free to hack on it 😄

@ekandreas
Copy link

Great! I'm using the "description" field with json-data right now. It would be great with meta fields instead :-)

@jbrooksuk
Copy link
Member

If we (or somebody) does this, I'd also like to see the same thing applied to Incidents. I reckon that'd be very useful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants