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

ES 2.0 + Marvel Compatibility #12

Closed
sscarduzio opened this issue Nov 11, 2015 · 1 comment
Closed

ES 2.0 + Marvel Compatibility #12

sscarduzio opened this issue Nov 11, 2015 · 1 comment

Comments

@sscarduzio
Copy link
Owner

Carrying over from a discussion in #11 with @ivukotic

Hi,

What marvel is trying to do is this:

curl -XPOST http://cl-analytics.mwt2.org:9200/.marvel-2015.11.10/_search -d '{"facets":{"query":{"terms":{"field":"node.name","size":100},"facet_filter":{"fquery":{"query":{"filtered":{"query":{"query_string":{"query":"_type:node_stats"}},"filter":{"bool":{"must":[{"range":{"@timestamp":{"from":1447119335396,"to":1447122935396}}}]}}}}}}}},"size":0}’

so I made what you suggested:
uri_re: ^http://._.marvel.__search.*

but the access is still not possible. Does it have to be on all the machines or only on the master node?

Thanks,
Ilija

@sscarduzio
Copy link
Owner Author

Hey @ivukotic, better late than ever: it was the wrong regex, sorry. The conf that works is this:

 readonlyrest:
    enable: true
    response_if_req_forbidden: <h1>Forbidden</h1>
    access_control_rules:
    - name: ALLOW MARVEL
      type: allow
      methods: [POST]
      uri_re: ^?\.marvel.*_search
    - name: readonly
      type: allow
      methods: [OPTIONS,GET]
      maxBodyLength: 0

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

No branches or pull requests

1 participant