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

[Merlindb] Unknown colums causes the module to crash #167

Closed
Seb-Solon opened this Issue Feb 8, 2012 · 7 comments

Comments

Projects
None yet
4 participants
@Seb-Solon
Contributor

Seb-Solon commented Feb 8, 2012

@Seb-Solon

This comment has been minimized.

Show comment
Hide comment
@Seb-Solon
Contributor

Seb-Solon commented Mar 14, 2012

@naparuba

This comment has been minimized.

Show comment
Hide comment
@naparuba

naparuba Jun 28, 2012

Owner

I'm wondering about deprecate this merlin module. It's a nightmare to manage (which version of the db to manage?) and use with Ninja is maybe not the best thing for Shinken.

Owner

naparuba commented Jun 28, 2012

I'm wondering about deprecate this merlin module. It's a nightmare to manage (which version of the db to manage?) and use with Ninja is maybe not the best thing for Shinken.

@naparuba

This comment has been minimized.

Show comment
Hide comment
@naparuba

naparuba Jun 28, 2012

Owner

So unless someone want to take the lead on this module, it will raise a deprecated warning in the 1.2 version, and a full remove in the next.

Owner

naparuba commented Jun 28, 2012

So unless someone want to take the lead on this module, it will raise a deprecated warning in the 1.2 version, and a full remove in the next.

@xkilian

This comment has been minimized.

Show comment
Hide comment
@xkilian

xkilian Aug 10, 2012

Contributor

I agree. The backends need to be simplified and unified. I have completed the cleanup of the wiki and website concerning Merlin.

Shinken is moving to MongoDB as the main state and configuration database and Graphite as the time-series database. Frontends should use the Livestatus API and/or directly as the WebUI.

Other backends will need to be reviewed as well as to their utility in the grand scheme of things.

Contributor

xkilian commented Aug 10, 2012

I agree. The backends need to be simplified and unified. I have completed the cleanup of the wiki and website concerning Merlin.

Shinken is moving to MongoDB as the main state and configuration database and Graphite as the time-series database. Frontends should use the Livestatus API and/or directly as the WebUI.

Other backends will need to be reviewed as well as to their utility in the grand scheme of things.

@xkilian

This comment has been minimized.

Show comment
Hide comment
@xkilian

xkilian Sep 2, 2012

Contributor

We need to identify that a Merlin module is trying to be loaded by the Arbiter and send out a warning (1.2.1) or Error and refusal to load the module for 1.4.

Contributor

xkilian commented Sep 2, 2012

We need to identify that a Merlin module is trying to be loaded by the Arbiter and send out a warning (1.2.1) or Error and refusal to load the module for 1.4.

@naparuba

This comment has been minimized.

Show comment
Hide comment
@naparuba

naparuba Sep 3, 2012

Owner

We can add a "state" value for the modules propeties (code part). With :

"dev"
"prod"
"We will delete it soon, so change your module"
"Sorry, it was deleted before and you forgot to look at your logs, maybe
the next time you will look at them".

...

Ok, maybe with real states messages :p

Jean

On Sun, Sep 2, 2012 at 6:05 AM, xkilian notifications@github.com wrote:

We need to identify that a Merlin module is trying to be loaded by the
Arbiter and send out a warning (1.2.1) or Error and refusal to load the
module for 1.4.


Reply to this email directly or view it on GitHubhttps://github.com//issues/167#issuecomment-8218863.

Owner

naparuba commented Sep 3, 2012

We can add a "state" value for the modules propeties (code part). With :

"dev"
"prod"
"We will delete it soon, so change your module"
"Sorry, it was deleted before and you forgot to look at your logs, maybe
the next time you will look at them".

...

Ok, maybe with real states messages :p

Jean

On Sun, Sep 2, 2012 at 6:05 AM, xkilian notifications@github.com wrote:

We need to identify that a Merlin module is trying to be loaded by the
Arbiter and send out a warning (1.2.1) or Error and refusal to load the
module for 1.4.


Reply to this email directly or view it on GitHubhttps://github.com//issues/167#issuecomment-8218863.

@Frescha

This comment has been minimized.

Show comment
Hide comment
@Frescha

Frescha Dec 4, 2012

Collaborator

This interface is no longer supported and is going to be completely removed from Shinken.

Collaborator

Frescha commented Dec 4, 2012

This interface is no longer supported and is going to be completely removed from Shinken.

@Frescha Frescha closed this Dec 4, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment