Marius Dammen

  • Total activity 31
  • Last activity
  • Member since
  • Following 0 users
  • Followed by 0 users
  • Votes 3
  • Subscriptions 11

Activity overview

Latest activity by Marius Dammen
  • Marius Dammen created a post,

    Add header support for json source

    Completed

    Headers are currently supported using a json sink, but it is not allowed with a json source.

  • Marius Dammen commented,

    The example above would look something like this: "sink": {"type": "json","system": "any-http-system","headers": {"X-API-Key-For-Method": "$SECRET(my-service-method-key)"},"url": "/ServiceMethodPro...

  • Marius Dammen created a post,

    Support for routing a response to another pipe

    Not planned

    When posting data to a service, it will sometimes return an array with e.g. an id, and a status on the individual record. This result can be merged back (correlated) into the source pipe in Sesam. ...

  • Marius Dammen created a post,

    Support for $SECRET in pipes

    Completed

    I see that $ENV is supported in pipes, but it seems like $SECRET doesn't work, is that correct? The context is sending an specific api key in a header for a specific GET/POST operation. That kind o...

  • Marius Dammen commented,

    The example shows a GET towards a service, the dynamic part is for filtering on a date in the initial request, this has still nothing to do with "per-entity-processing". As with regards to delegati...

  • Marius Dammen commented,

    Json and rest are typical sinks that would benefit here. We see that some url/http based services run validation on the json payload they receive, and the "_id" field typically makes it non-valid.

  • Marius Dammen commented,

    As mentioned, this is not regarding "per entity processing", it is a shared concern when configuring the pipe (see the url attribute below): {"_id": "pipe-with-date","type": "pipe","source": {"type...

  • Marius Dammen commented,

    This is mostly a concern when managing microservices. The Sesam system configuration allows custom allocation for memory assigned to the docker container. Without knowing how much memory a node can...

  • Marius Dammen created a post,

    Memory consumption

    Answered

    The subscription page does not list the available amount of memory available for a node. There is also no metrics showing the amount of memory used. This would make it easier to foresee bottlenecks...

  • Marius Dammen commented,

    This is not for the urls per entity, it is for the url to the system (source/sink). As far as I know, there is no way of supplying dynamic arguments (like dates) to it. For you suggestion, I would ...